Hanzo
OpenapiIam

Mints an access token for the `?id=<owner>/<name>` target user (optional… — POST /v1/iam/tokens/issue

Mints an access token for the `?id=<owner>/<name>` target user (optional `?aud=` resource, RFC 8707), issued by the authenticated + allow-listed…

POST /v1/iam/tokens/issue

Addresshttps://api.hanzo.ai/v1/iam/tokens/issue
MethodPOST
Operationpost_iam_tokens_issue
AuthAuthorization: Bearer $HANZO_API_KEY

Mints an access token for the ?id=<owner>/<name> target user (optional ?aud= resource, RFC 8707), issued by the authenticated + allow-listed confidential client. The token's subject + owner are the TARGET USER's, so a resource server scopes on the validated owner claim to the user's tenant — indistinguishable from a token the user obtained directly. Response is the camelCase {accessToken, expiresIn} body identity.ts consumes. Equivalent to the RFC 8693 token-exchange grant, minus the subject_token proof (the console has the user's id, not a token) — the reason this compat shim exists.

Request

The document declares no body for POST /v1/iam/tokens/issue. 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_tokens_issue, 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 tokens issue

IAM API · All Hanzo APIs · Interactive reference

How is this guide?

On this page