Hanzo
OpenapiIam

(re)generates the target user's key of the requested TYPE and returns it once,… — POST /v1/iam/mint-user-keys

(re)generates the target user's key of the requested TYPE and returns it once, over the shared authorizeMinter + mintTarget seam.

POST /v1/iam/mint-user-keys

Addresshttps://api.hanzo.ai/v1/iam/mint-user-keys
MethodPOST
Operationpost_iam_mint-user-keys
AuthAuthorization: Bearer $HANZO_API_KEY

(re)generates the target user's key of the requested TYPE and returns it once, over the shared authorizeMinter + mintTarget seam. ?type=secret (the default) yields the confidential sk-; ?type=publishable yields the pk- that is safe to ship in client JS and resolves to an org, never a principal.

It writes the schema.Key row that the resolvers actually read. schema.User.AccessKey is not a credential and nothing resolves it, so a key stamped there would authenticate nobody.

Request

The document declares no body for POST /v1/iam/mint-user-keys. 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_iam_mint-user-keys, 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 iam mint-user-keys

IAM API · All Hanzo APIs · Interactive reference

How is this guide?

On this page