device_first_key_unavailable
HTTP 409§9.10 Agreements
Device bootstrap can claim only the never-delivered provisioning Default key. If a browser/device handoff already delivered it, this route never mints another key; a customer who lost every delivered key needs staff-assisted recovery.
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_first_key_unavailable",
"title": "…",
"status": 409,
"detail": "…",
"instance": "/v1/…"
}