Hanzo
OpenapiAccount

Set your profile photo

Stores one image as the signed-in user's profile photo and answers the URL it is served from, which is also written to the user's IAM record — so every…

POST /v1/account/avatar

Addresshttps://api.hanzo.ai/v1/account/avatar
MethodPOST
Operationpost_account_avatar
AuthAuthorization: Bearer $HANZO_API_KEY

Stores one image as the signed-in user's profile photo and answers the URL it is served from, which is also written to the user's IAM record — so every surface that already renders avatar picks it up with no further call.

The body is a multipart form with a file part. The format is decided by the BYTES, never the filename or the part's Content-Type: png, jpeg, gif and webp are accepted and everything else is refused with 415, so an SVG cannot be stored as a picture and later served as a program. Over 8 MiB is 413; empty is 400.

The photo is addressed by the sha256 of its bytes, so setting a new one yields a new URL rather than a stale cache of the old face. The caller is taken from the validated identity ONLY — there is no way to name a different subject — so this always sets your own photo, and a caller with no organization yet is refused.

Request

The document declares no body for POST /v1/account/avatar. 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_account_avatar, 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 has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.


Account API · All Hanzo APIs · Interactive reference

How is this guide?

On this page