Mints an access token for the `?id=<owner>/<name>` target user (optional… — POST /v1/iam/issue-user-token
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/issue-user-token
| Address | https://api.hanzo.ai/v1/iam/issue-user-token |
| Method | POST |
| Operation | post_iam_issue-user-token |
| Auth | Authorization: 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/issue-user-token. 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_issue-user-token, 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 issue-user-tokenimport { Configuration, IamApi } from 'hanzoai';
const api = new IamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postIamIssue-user-token();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import IamApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = IamApi(client).post_iam_issue-user-token()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.IamAPI.PostIamIssue-user-token(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, iam_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = iam_api::post_iam_issue-user-token(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.IamApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new IamApi(client).postIamIssue-user-token();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl -X POST https://api.hanzo.ai/v1/iam/issue-user-token \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches iam through the iam tool, which names its 75 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list__well_known_jwks"
}
}
}'How is this guide?