Hanzo
OpenapiCommerce

Create a subscriber

A subscriber is a mailing-list member — name, email, the form id that captured them, unsubscribed state and date, client details, tags and metadata.

POST /v1/commerce/subscriber/

Addresshttps://api.hanzo.ai/v1/commerce/subscriber/
MethodPOST
Operationpost_commerce_subscriber
AuthAuthorization: Bearer $HANZO_API_KEY

A subscriber is a mailing-list member — name, email, the form id that captured them, unsubscribed state and date, client details, tags and metadata. Writing one FIRES A WEBHOOK: subscriber.created on create and subscriber.updated on replace or patch, emitted BEFORE the write is known to have succeeded and carrying the row as sent, so the payload holds the raw email rather than the normalized one that gets stored. 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 token must also carry Admin or WriteSubscriber.

Request

The document declares no body for POST /v1/commerce/subscriber/. 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_subscriber, 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 subscriber create

Commerce API · All Hanzo APIs · Interactive reference

How is this guide?

On this page