Forms
PUT
Update Form
PUT /v1/forms/{formId}Update an existing form's configuration (DRAFT forms only).
Use Cases:
- Update fieldMapping (contact property mappings)
- Update the fieldMapping (contact property mappings)
- Update form name, description, or settings
- Configure SEO metadata
Behavior:
- Only DRAFT forms can be updated
- PUBLISHED and ARCHIVED forms are immutable
- To update published forms, create a new version first
- All fields are optional (partial updates supported)
- If fieldMapping changes and form has deployed HTML, cross-validation runs automatically
Required Scope: write:forms
Updatable Fields (DRAFT only):
- name (internal identifier)
- description (form purpose)
- fieldMapping (field name to contact property mapping)
- settings (success action, double opt-in)
- SEO fields (seoTitle, seoDescription, seoImageUrl, seoFaviconUrl, slug)
Update Workflow for Published Forms:
- Create new version: POST /v1/forms/{formId}/versions
- Update the new DRAFT version: PUT /v1/forms/{newVersionId}
- Publish the updated version: POST /v1/forms/{newVersionId}/publish
- Previous published version automatically becomes ARCHIVED
Note: For published forms, create a new version instead of updating directly.
Path parameters
formIdstringrequiredForm ID
Bodyrequired
namestringMin length: 1Max length: 200
descriptionanytype"SIGN_UP" | "SURVEY"display"POPUP" | "INLINE_EMBED"fieldMappingobjectsettingsobjectdoubleOptInEmailIdanyseoTitleanyseoDescriptionanyseoImageUrlanyseoFaviconUrlanysluganyResponse
200Form updated successfully with refreshed updatedAt timestamp. Form remains in DRAFT status.
objectstringrequiredidstringrequiredUnique form identifier