Hanzo
OpenapiCommerce

Create a submission

A submission is one filled-in form from a site visitor — an email, an optional user id, the client details the server observed (user agent, referer,…

POST /v1/commerce/submission/

Addresshttps://api.hanzo.ai/v1/commerce/submission/
MethodPOST
Operationpost_commerce_submission
AuthAuthorization: Bearer $HANZO_API_KEY

A submission is one filled-in form from a site visitor — an email, an optional user id, the client details the server observed (user agent, referer, geography) and the form's own fields as free metadata. It carries no form id, so the link back to the form that produced it is not stored on the row. Decodes the body into a new row in the caller org's own namespaced store — isolated to that tenant from its first write — and answers the stored row at 201 with a Location header naming its id. The id is assigned by the store, not taken from the body. A body that fails to decode is 400 and a store that refuses the write is 500. Any valid access token reaches it. The per-kind permission table has no entry for submission, so the scaffold skips that second check with a warning and the gate above is the whole authorization story.

Request

The document declares no body for POST /v1/commerce/submission/. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask the MCP door's describe for post_commerce_submission, which answers from the running route.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo commerce submission create

Commerce API · All Hanzo APIs · Interactive reference

How is this guide?

On this page