# Create info

URL: https://docs.hanzo.ai/docs/openapi/iam/post-iam-oauth-device-info

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

`POST /v1/iam/oauth/device/info`

> [IAM →](https://docs.hanzo.ai/docs/openapi/iam) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides)

|               |                                                 |
| ------------- | ----------------------------------------------- |
| **Address**   | `https://api.hanzo.ai/v1/iam/oauth/device/info` |
| **Method**    | `POST`                                          |
| **Operation** | `post_iam_oauth_device_info`                    |
| **Auth**      | `Authorization: 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 MCP'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](https://docs.hanzo.ai/docs/errors).

## Examples

**CLI**

```bash
hanzo iam oauth device info
```

**SDK**

**.ts**

```ts
import { Configuration, IamApi } from 'hanzoai';

const api = new IamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postIamOauthDeviceInfo();
```

**.py**

```python
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_oauth_device_info()
```

**.go**

```go
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.IamAPI.PostIamOauthDeviceInfo(context.Background()).Execute()
if err != nil {
	return err
}
```

**.rs**

```rust
use hanzo_client::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_oauth_device_info(&cfg, Default::default()).await?;
```

**.java**

```java
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.IamApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new IamApi(client).postIamOauthDeviceInfo();
```

**HTTP**

```bash
curl -X POST https://api.hanzo.ai/v1/iam/oauth/device/info \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

MCP reaches **iam** through the `iam` tool, which names its 44 operations with its own verbs — this one among them, under a name only MCP declares. `describe` explains any of them:

```bash
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_iam_applications"
         }
       }
     }'
```

---

[IAM API](https://docs.hanzo.ai/docs/openapi/iam) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)