The single POST endpoint routes to one of four operations, based on which fields are present in the request.
Properties
hydrationRecordId
applicationData
Operation
Absent
Present
CREATE—creates an application tree and returns the full tree with the assigned Salesforce IDs.
Present
Absent
READ—hydrates and returns the existing tree.
Present
Present, with no _delete markers
UPDATE or CREATE—updates changed nodes and creates nodes without an ID in one atomic call.
Present
Present, with _delete markers
DELETE—soft-deletes the marked nodes, and can be combined with updates and creates in the same call.
Send DATETIME field values with milliseconds (for example, 2026-02-01T06:30:00.000Z) or as a date (yyyy-MM-dd). A DATETIME value without milliseconds is set to null when the record is created.
On update and delete, include the id field on the root ApplicationForm node. If id is missing when hydrationRecordId is present, new child records and all _delete markers in the payload are dropped.
Deletion is explicit for each node. Mark every node to delete with "_delete": true. If you mark a parent node but don’t mark its RESTRICT-constraint child records in the same request, the call fails with HTTP status code 409 and the error code DELETE_NOT_ALLOWED, and all changes are rolled back.
Deletion is soft. Deleted records go to the Recycle Bin and are recoverable for about 15 days. Hard delete isn’t supported.
j