Error reference / device-access-denied
Approval was declined
The sign-in was denied in the dashboard, or the workspace cannot hold API keys.
| Problem type | /problems/device-access-denied |
|---|---|
| HTTP status | 403 |
| Emitted by | REST API (/v1) |
| Title values | Approval was declined |
| Trigger | REST API (/v1): the human declined, or the workspace cannot hold API keys (Personal) |
What happened
POST /v1/device/token found the sign-in request denied. Either a person clicked Deny on the approval page, or the workspace that opened the page is on the Personal plan, which has no API access, so the page denied it on their behalf. The response is HTTP 403 with this slug.
What it means
No key was created. A denied code cannot be approved later; it is finished.
What to do next
If a person denied it by mistake, start a new sign-in from your client and approve the new code. If the workspace is on Personal, API keys require the Pro plan; upgrade from Billing in the dashboard, then sign in again.
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-access-denied",
"title": "Approval was declined",
"status": 403,
"instance": "/v1/...",
"docs_url": "https://docs.signenvoy.com/errors/device-access-denied"
}