Form Handler Object

Form handlers are an alternative to Account Engagement forms. You can use a form handler to integrate your third-party or custom forms with Account Engagement to track submission data. Learn more about form handlers in Salesforce Help.

The API to access the Form Handler object follows the conventions described in Version 5 Overview.

Operation	HTTP Verb	URL Format	Ability Requirements
Create	`POST`	`https://pi.pardot.com/api/v5/objects/form-handlers`	Marketing > Forms > Form Handlers > Create
Read	`GET`	`https://pi.pardot.com/api/v5/objects/form-handlers/<id>?<params>`	Marketing > Forms > Form Handlers > View
Update	`PATCH`	`https://pi.pardot.com/api/v5/objects/form-handlers/<id>`	Marketing > Forms > Form Handlers > Create
Delete	`DELETE`	`https://pi.pardot.com/api/v5/objects/form-handlers/<id>`	Marketing > Forms > Form Handlers > Delete
Query	`GET`	`https://pi.pardot.com/api/v5/objects/form-handlers?<params>`	Marketing > Forms > Form Handlers > View
Add Tag	`POST`	`https://pi.pardot.com/api/v5/objects/form-handlers/<id>/do/addTag`	Marketing > Forms > Form Handlers > Create AND Marketing > Segmentation > Tags > Create
Remove Tag	`POST`	`https://pi.pardot.com/api/v5/objects/form-handlers/<id>/do/removeTag`	Marketing > Forms > Form Handlers > Create AND Marketing > Segmentation > Tags > Create

These fields are required only for the create operation.

Field	Type	Description
`name`	String	Name of the object for identification in Account Engagement.
`folderId`	Integer	ID of the folder containing this object.
`campaignId`	Integer	The ID of the campaign associated with this object.

Field	Type	Description
`trackerDomainId`	Integer	The ID of the tracker domain associated with this object.
`isDataForwarded`	Boolean	When `true`, enables data forwarding to the success location.
`successLocation`	String	The URL the user is forwarded to if the submission is successful.
`errorLocation`	String	The URL the user is forwarded to if the submission has an error.
`isAlwaysEmail`	Boolean	When `true`, disables visitor activity throttling and sends autoresponder emails after every submission. Learn more about throttling in Salesforce Help.
`isCookieless`	Boolean	When `true`, the form handler is in Kiosk/Data Entry Mode, and does not cookie browser as a submitted prospect.

Field	Type	Description
`id`	Integer	ID of this object.
`salesforceId`	String	Salesforce Id of the object.
`embedCode`	String	Code to embed this form handler in a webpage.
`createdAt`	DateTime	Creation time of this object.
`createdById`	Integer	ID of the user who created the object.
`isDeleted`	Boolean	True if the object is in the Account Engagement recycle bin.
`updatedById`	Integer	ID of the user who last updated the object.
`createdBy`	User	User object representing the user who created the object. See documentation for User for fields.
`updatedBy`	User	User object representing the user who last updated the object. See documentation for User for fields.
`campaign`	Campaign	Campaign object representing the campaign that was set on Create. See documentation for Campaign for fields.
`folder`	Folder	JSON object representing the folder for this object. See documentation for Folder for fields.
`trackerDomain`	Tracker Domain	Tracker Domain object representing the tracker domain associated with the form handler. See documentation for Tracker Domain for fields.

Create a single form handler following the conventions described in the Version 5 Overview.

When form handlers are created, an email field is included automatically.

Example request:

Example response:

Retrieve a single form handler object following the conventions described in the Version 5 Overview.

Example request:

Example Response

Updating a form handler follows the conventions described in the Version 5 Overview.

Deleting a form handler follows the conventions described in the Version 5 Overview.

Retrieving a collection of form handlers follows the conventions described in Version 5 Overview.

When executing a query, the following fields can be specified in the orderBy parameter. See the conventions for query described in the Version 5 Overview.

id
createdAt

Example Request

Example Response

When executing a query, the following parameters can be used to filter the returned results. These parameters can be specified in the request along with any shared parameters defined in Version 5 Overview. When specifying more than one parameter, all parameters must match the record in order for it to be returned in the results.

Parameter	Description
`id`	Returns any form handler where ID is equal to the given integer value.
`idList`	Returns any form handler where ID is included in the given list of values.
`idGreaterThan`	Returns any form handler where ID is greater than the specified value, non-inclusive.
`idGreaterThanOrEqualTo`	Returns any form handler where ID is greater than or equal to the specified value.
`idLessThan`	Returns any form handler where ID is less than the specified value, non-inclusive.
`idLessThanOrEqualTo`	Returns any form handler where ID is less than or equal to the specified value.
`name`	Returns any form handler where Name is equal to the given string value.
`createdAt`	Returns any form handler where CreatedAt is equal to the given datetime value.
`createdAtAfter`	Returns any form handler where CreatedAt is after the given datetime value, non-inclusive.
`createdAtAfterOrEqualTo`	Returns any form handler where CreatedAt is after or equal to the given datetime value.
`createdAtBefore`	Returns any form handler where CreatedAt is before the given datetime value, non-inclusive.
`createdAtBeforeOrEqualTo`	Returns any form handler where CreatedAt is before or equal to the given datetime value.
`deleted`	Determines whether to return deleted records. The value can be `false` (default), `true`, or `all`.

Example Request

Example Response

Adds a Tag to the Form Handler object, which creates a TaggedObject.

Example Request

Example Response

Remove a tag from a Form Handler object. When you remove a tag, the associated TaggedObject record is deleted.

Example Request

Example Response

Returns code 204 no content.