Error reference / device-code-expired
Sign-in request expired or already used
The device code is unknown, past its expiry, or was already claimed.
| Problem type | /problems/device-code-expired |
|---|---|
| HTTP status | 400 |
| Emitted by | REST API (/v1) |
| Title values | This sign-in request has expired or was used. Start again |
| Trigger | REST API (/v1): device code unknown, expired, or already claimed (indistinguishable) |
What happened
POST /v1/device/token was called with a device_code the gateway will not honor: it was never issued, its ten-minute window has passed, or it was already exchanged for a key. The response is HTTP 400 with this slug. The three cases are deliberately indistinguishable.
What it means
No key will be issued for this code. If the code had been approved and claimed once, the key from that claim is the only one that exists.
What to do next
Start a new sign-in from your client (POST /v1/device/code) to get a fresh code, and approve it within ten minutes.
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-code-expired",
"title": "This sign-in request has expired or was used. Start again",
"status": 400,
"instance": "/v1/...",
"docs_url": "https://docs.signenvoy.com/errors/device-code-expired"
}