Hanzo
OpenapiCommerce

Create a disclosure

A disclosure is a published-document record — a publication body, a content hash, a type and a named receiver.

POST /v1/commerce/disclosure/

Addresshttps://api.hanzo.ai/v1/commerce/disclosure/
MethodPOST
Operationpost_commerce_disclosure
AuthAuthorization: Bearer $HANZO_API_KEY

A disclosure is a published-document record — a publication body, a content hash, a type and a named receiver. The hash LOOKS like a field you set and is in fact derived, but only on update: a freshly created disclosure keeps whatever hash the caller sent until the first replace or patch recomputes it, so a new row's hash attests to nothing. This kind lives in commerce's demo tree — a live writable resource in your tenant's real store that nothing else in commerce reads. 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 disclosure, 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/disclosure/. 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_disclosure, 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 disclosure create

Commerce API · All Hanzo APIs · Interactive reference

How is this guide?

On this page