Submit a signed form

Validates authoritatively and persists the filing. The instance id pins the catalog form and revision being submitted. The signature is stamped server-side from the authenticated session (signer identity, timestamp, IP, user agent) — the client supplies only the consent flag. The Idempotency-Key header is forwarded to the forms service, which requires it for safe retries.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Form instance id from the checklist item's id (opaque; not the catalog form id)

Body Params
string
required

Engagement context the filing is scoped to

string
required

Catalog version being submitted (stale version → 409)

data
object
required

Visible-field answers, keyed by catalog fieldKey

signature
object
required
Headers
string
length between 1 and 255
^[\x21-\x7e]{1,255}$

Idempotency token forwarded to the forms service for safe retries (UUID recommended)

Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json