Hanzo
OpenapiContent

Returns the ONE marketing-content state machine: the ordered lifecycle states,…

Returns the ONE marketing-content state machine: the ordered lifecycle states, which state a fresh document starts in, which one is publicly live, and the…

GET /v1/content/lifecycle

Addresshttps://api.hanzo.ai/v1/content/lifecycle
MethodGET
Operationget_content_lifecycle
AuthAuthorization: Bearer $HANZO_API_KEY

Returns the ONE marketing-content state machine: the ordered lifecycle states, which state a fresh document starts in, which one is publicly live, and the legal successors of every state. The console builds its board columns and its per-item action buttons from this single answer, so the UI and the write-time enforcement hook can never disagree about what is legal.

Request

GET /v1/content/lifecycle takes no parameters and no body — the credential is the whole request.

Response

StatusBodyMeaning
200stateGraphok

200 body — 5 fields.

FieldInTypeAlwaysDescription
initialbodystringInitial is the state a fresh document starts in — "draft".
livebodystringLive is the ONE state that is publicly readable — "published".
statesbodystring[]States is every lifecycle state in canonical order: draft, in_review, approved, queued, published, archived.
transitionsbodyobjectTransitions maps each state to the states it may move to.
transitions.*bodystring[]

Failure carries the platform error shape — see Errors.

Examples

hanzo content lifecycle

Content API · All Hanzo APIs · Interactive reference

How is this guide?

On this page