Mass-Updating Forms

Are we able to append fields to existing forms using the update endpoint

You add with the /fields.json endpoint.

How is existing form logic handled when updating a form? i.e. layers of visibility rules and progressive profiling

There's an endpoint for VRs, /visibility.json. ProgPro is considered a pseudo-field in itself.

You can learn a lot more by reverse-engineering forms. The methods are not all totally clear from the docs (though, to be fair it, it's one of the most complete doc sections on the Developer site -- it's just really complex).

How can we mass export all approved form names with their ID numbers?

The main /forms.json endpoint.

Is it possible to update all of the Marketo landing pages where these forms live at the same time?

Approving LP Templates and LPs is done via those other endpoints, not the Forms endpoints.

Is it possible to see what non-Marketo pages are using our forms?

No, not if you haven't already set up some kind of auditing process (i.e. using the Munchkin API to send an activity to Marketo when a form is loaded).

@Sanford Whiteman‌

I'm having this similar problem of mass needing to update forms (need to switch out an old field for a new one)- which I think I have found the solution above, so thanks everyone. 

However, my question now is... 

Is there a simple/ mass way to update all campaign flow steps that use the old field, to the new field?

For example... 

Right now we ask for Job Title, but need to switch to a new field we have created call Job Function. We have workflows based on whether people indicate a certain Job Title, which will now need to change to Job Function in order to operate correctly. 

Is there an easy way to a) identify which flows use this old field and b) update them to the new one?

Look forward to your help, thanks!