Hanzo
OpenapiGuide

Replace your org's journey with a curriculum you author

Sets the caller org's OWN curriculum — the per-customer override — and answers the journey now in force with `custom: true`.

PUT /v1/guide/curriculum

Addresshttps://api.hanzo.ai/v1/guide/curriculum
MethodPUT
Operationput_guide_curriculum
AuthAuthorization: Bearer $HANZO_API_KEY

Sets the caller org's OWN curriculum — the per-customer override — and answers the journey now in force with custom: true. The body is a curriculum document, and it is accepted as YAML or JSON: that is the caller-visible reason this takes a raw body rather than a declared shape. Whatever the syntax, the CANONICAL parsed form is what is stored, so the document the engine runs never depends on how it was written.

Fail-closed: a body that does not parse, or parses but is not a valid journey (unique step ids, no dangling or cyclic dependencies), is 422 and NEVER becomes active — the org keeps the journey it had. Requires a validated org; 403 without one. An empty body is 400 and one over 256 KiB is 413.

This is tier one only. It overrides nothing but this org's own journey; the shared brand blueprint is a different surface with a different gate. DELETE the same path to drop the override and fall back to it.

Request

The document declares no body for PUT /v1/guide/curriculum. 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 put_guide_curriculum, 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 guide curriculum replace

Guide API · All Hanzo APIs · Interactive reference

How is this guide?

On this page