Approval was declined

The sign-in was denied in the dashboard.

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 (D85 retired the second cause, a Personal workspace)

What happened

POST /v1/device/token found the sign-in request denied: a person clicked Deny on the approval page. 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 it was denied by mistake, start a new sign-in from your client and approve the new code.

Problem body

Every error the API returns 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://staging.signenvoy-docs-b4g.pages.dev/errors/device-access-denied"
}