# Issue an IAM token

> Issues a short-lived token that acts as the calling API key held to a bound: policy, an inline policy document, or policy_ids, policies of the key's project…

Issues a short-lived token that acts as the calling API key held to a bound: `policy`, an inline policy document, or `policy_ids`, policies of the key's project or global ones. Every request on the token is authorized against the key's grant as it stands at that request ∩ the bound, so an `Allow` beyond the key grants nothing and a permission removed from the key leaves the token too. Work the token starts (a generation, a session turn, a task dispatch, an orchestration run, a playbook version) keeps the bound after the token expires. Only an API key scoped to a project issues one (`403 IAM_TOKEN_ISSUER_NOT_ALLOWED`); a token creates neither tokens nor API keys. The audit log records the token's `jti` and `principal` under `detail.iam_token` on every entry the token makes.

  Request

<RequestSchema
  {...require("./create-iam-token.RequestSchema.json")}
>

<StatusCodes
  {...require("./create-iam-token.StatusCodes.json")}
>
