Hanzo
OpenapiIam

Answers "what am I approving?" for a pending device code.

Answers "what am I approving?" for a pending device code.

POST /v1/iam/oauth/device/info

Addresshttps://api.hanzo.ai/v1/iam/oauth/device/info
MethodPOST
Operationpost_iam_oauth_device_info
AuthAuthorization: Bearer $HANZO_API_KEY

Answers "what am I approving?" for a pending device code.

The approval page exists to tell a human WHICH application they are authorizing; a page that names any other one defeats the control it implements. The client is a property of the CODE, not of the page or of whatever app the browser happens to be signed in to, so it is read from the code's row here and nowhere else.

Requires a signed-in session, and answers with the same ONE opaque refusal approveDevice uses. That is deliberate: the user_code is only 40 bits and is the one secret in this flow, so an unauthenticated lookup — or one that distinguished unknown from expired from already-approved — would be an oracle for hunting live codes. Gated and opaque, it reveals strictly less than the approval the same caller could already attempt.

Request

The document declares no body for POST /v1/iam/oauth/device/info. 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_oauth_device_info, 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 oauth device info

IAM API · All Hanzo APIs · Interactive reference

How is this guide?

On this page