Basic

Partially update a form definition

Update an existing form in your HubSpot account by specifying the form ID. This operation allows you to modify the form's properties, such as its name, field groups, configuration, display options, legal consent options, and archived status. This is useful for keeping forms up to date with your current marketing strategies or compliance requirements.

patch/marketing/forms/2026-09-beta/{formId}

Path parameters

formIdstring required

Request body

archivedboolean

Whether this form is archived.

namestring

The name of the form. Expected to be unique for a hub.

Response

successful operation

archivedboolean required

archivedAtstring date-time

createdAtstring date-time required

formType'hubspot' required

idstring required

namestring required

updatedAtstring date-time required

Changes

Changed in 6 of the 55 revisions of this API.226

Aug 17, 20262026-09-beta12cd90f1eb181See the full diff
- ○
  endpoint added
  endpoint-added
Jul 13, 20262026-09-beta0a2f094f9ab41See the full diff
- ▲
  api path removed without deprecation
  api-path-removed-without-deprecation
May 22, 20262026-09-beta36245144443e2See the full diff
- ○
  the security scope forms was added to the endpoint's security scheme oauth2
  api-security-scope-added
- ○
  the security scope forms-write was removed from the endpoint's security scheme oauth2
  api-security-scope-removed
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
May 14, 20262026-09-betab74d391e3e8310See the full diff
- ○
  the response property //// became required for the status
  response-property-became-required
- ○
  the response property //// became required for the status
  response-property-became-required
- ○
  the response property //// became required for the status
  response-property-became-required
- ○
  the response property //// became required for the status
  response-property-became-required
- ○
  the response property //// became required for the status
  response-property-became-required
- ○
  the response property //// became required for the status
  response-property-became-required
- ○
  the response property //// became required for the status
  response-property-became-required
- ○
  the response property //// became required for the status
  response-property-became-required
- ○
  the response property //// became required for the status
  response-property-became-required
- ○
  the response property //// became required for the status
  response-property-became-required
May 13, 20262026-09-betadb0d2eb4691d112See the full diff
- ▲
  the /// response's property type changed from no type to object for status
  response-property-type-changed
- ○
  added the optional property //// to the response with the status
  response-optional-property-added
- ○
  added the optional property //// to the response with the status
  response-optional-property-added
- ○
  added the optional property //// to the response with the status
  response-optional-property-added
- ○
  added the optional property //// to the response with the status
  response-optional-property-added
- ○
  added the optional property //// to the response with the status
  response-optional-property-added
- ○
  added the optional property //// to the response with the status
  response-optional-property-added
- ○
  added the optional property //// to the response with the status
  response-optional-property-added
- ○
  added the optional property //// to the response with the status
  response-optional-property-added
- ○
  added the optional property //// to the response with the status
  response-optional-property-added
- ○
  added the optional property //// to the response with the status
  response-optional-property-added
- ○
  added the optional property //// to the response with the status
  response-optional-property-added
- ○
  removed subschema #2 from the /// response property allOf list for the response status
  response-property-all-of-removed
May 4, 20262026-09-beta78d0073d16371See the full diff
- ○
  endpoint added
  endpoint-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history