---
title: "Device Verify"
method: POST
path: "/api/v1/oauth/device/verify"
tags: ["oauth2-server"]
---

# Device Verify

`POST /api/v1/oauth/device/verify`

## Request

- Base URL: `https://memory.kagura-ai.com` (the document declares no server; this is the origin it was published from)
- URL: `https://memory.kagura-ai.com/api/v1/oauth/device/verify`
- Auth: none declared

Look up a pending device authorization by user_code.

Returns enough information for the browser consent screen to render
(client_name, scope). No authentication required — possession of the
user_code is the bearer token for this lookup.

Limited per client address to ``oauth_device_verify_rate_limit_per_minute``
requests per minute, found or not (RFC 8628 §5.1, #1656). Over the limit it
returns 429 with ``Retry-After`` before the lookup runs.

## Request body

- DeviceVerifyRequest: Request to look up pending device authorization by user_code.
  - `user_code` string, required

## Response `200`

Successful Response

- DeviceVerifyResponse: Pending device authorization info returned for the consent screen.
  - `user_code` unknown, required
  - `client_name` unknown, required
  - `scope` unknown, required
  - `expires_at` unknown, required
  - `is_authorized` unknown, required
  - `is_expired` unknown, required

## Other responses

- `422`: Validation Error
- `429`: Too many user code lookups from this address

---

[API](https://skmtc.dev/kagura-ai/apis/kagura-memory-cloud.md) · [All operations](https://skmtc.dev/kagura-ai/apis/kagura-memory-cloud/llms.txt) · [OpenAPI document](https://skmtc.dev/kagura-ai/apis/kagura-memory-cloud/revisions/09f17f5ada29?raw)