Save data for multiple sections in a single request
Accepts a JSON object keyed by section name. Each value is the same payload shape as PUT /sections/. Validation is atomic: all sections are validated before any data is saved, and if any section fails validation the entire request is rejected. Saves are sequential: after validation passes, sections are persisted one at a time. Array sections use upsert semantics: items with refId update existing entities, items without refId create new entities. Existing entities not included are preserved. The response data field is an object keyed by section name containing the saved data for each section.
Authorizations
Bearer token obtained via Circle key exchange
Path Parameters
Application UUID
Body
JSON object keyed by section name. Each value matches the section's JSON Schema.
Section data keyed by section name — structure varies by template. Consult GET /{applicationId}/schema.
Response
All section statuses after save
Saved section field data — structure varies by application template. For single-section saves this is the section payload directly. For bulk saves this is an object keyed by section name. Retrieve the shape via GET /{applicationId}/schema.