device_authorization_invalid
HTTP 400§9.10 Agreements
The submitted human code is malformed, absent, expired, consumed, or bound to a different owner/workspace. Those cases intentionally share one response so the approval endpoint is not a pairing-code oracle.
Problem shape
Every non-2xx response is an RFC 9457 application/problem+json body. The type URI below is stable and machine-matchable, so branch on the final path segment (the code) and treat the status as redundant confirmation. See the error-handling guide.
{
"type": "https://docs.vocapable.com/errors/device_authorization_invalid",
"title": "…",
"status": 400,
"detail": "…",
"instance": "/v1/…"
}