Issue an IAM token
POST/api/v1/iam/tokens
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
Responses
- 201
- 400
- 401
- 403
- 413
- 429
- 500
- 502
- 4XX
The token and when it expires
Invalid request — a query parameter or body field the operation does not declare, or a value that fails validation
Unauthorized
Insufficient permissions
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there