Error reference / device-authorization-pending
Waiting for approval in the browser
The device-flow sign-in has not been approved yet; keep polling.
| Problem type | /problems/device-authorization-pending |
|---|---|
| HTTP status | 400 |
| Emitted by | REST API (/v1) |
| Title values | Waiting for approval in the browser |
| Trigger | REST API (/v1): device-flow poll before the human approved (D46(a)) |
What happened
POST /v1/device/token was called before anyone approved the sign-in in the dashboard. The response is HTTP 400 with this slug. This is the normal state of a device-flow login between the client printing its code and a person clicking Approve.
What it means
Nothing is wrong and nothing was created. The code is still live for expires_in seconds from when it was issued.
What to do next
Keep polling POST /v1/device/token every interval seconds with the same device_code. Open verification_uri_complete in a browser, sign in to the workspace that should own the key, check what the page says it will create, and approve. The next poll returns the key.
Problem body
Every error is an RFC 9457 problem document with media type
application/problem+json. The type member is the
stable identifier to switch on; docs_url is this page.
{
"type": "/problems/device-authorization-pending",
"title": "Waiting for approval in the browser",
"status": 400,
"instance": "/v1/...",
"docs_url": "https://docs.signenvoy.com/errors/device-authorization-pending"
}