Hanzo
OpenapiPref

Save the preference keys your surface owns, leaving every other key alone

Merges a JSON object key-wise into the signed-in caller's OWN preference document and answers with the whole document after the merge, so a surface saves…

PATCH /v1/pref

Addresshttps://api.hanzo.ai/v1/pref
MethodPATCH
Operationpatch_pref
AuthAuthorization: Bearer $HANZO_API_KEY

Merges a JSON object key-wise into the signed-in caller's OWN preference document and answers with the whole document after the merge, so a surface saves theme without having to send back the density another surface owns. The merge is SHALLOW and the key space is open: an unnamed key is left untouched, a named key is replaced whole, and a key sent with a null value is DELETED. The subject is the <owner>/<name> identity built from the validated credential and is the mandatory predicate on the write, so there is no path to another user's preferences — not for an org admin, not for a platform SuperAdmin. Fails closed: no validated principal is 403; an empty body or a literal null is 400; and a patch or a resulting document over 16 KiB or 128 keys is 413.

Request

The document declares no body for PATCH /v1/pref. 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 patch_pref, 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 prefs patch

Pref API · All Hanzo APIs · Interactive reference

How is this guide?

On this page