Error reference / auth-level-unavailable
Authentication level not available
A recipient asked for the account or passkey level; only link and otp exist today.
| Problem type | /problems/auth-level-unavailable |
|---|---|
| HTTP status | 422 |
| Emitted by | REST API (/v1) |
| Title values | Authentication level not available |
| Trigger | REST API (/v1): a recipient asks for the `account` or `passkey` authentication level, which ship with signer accounts (M6); only `link` and `otp` are accepted (D55) |
What happened
A request that creates or replaces recipients (POST /v1/documents, PUT /v1/documents/{id}/recipients, POST /v1/templates, POST /v1/templates/{id}/use) included a recipient whose auth_level is account or passkey. Those levels are verified against a signer account, which ships in a later milestone. The response is HTTP 422 and nothing was created or changed.
What it means
Two levels are available now. link (the default) relies on the signing link sent to the recipient’s address. otp adds a one-time code emailed to that address, which the recipient enters before the document opens; the satisfied level is recorded in the audit trail and printed on the certificate page. The API refuses the unavailable levels rather than storing a promise it cannot enforce.
What to do next
Send link or otp for each recipient and retry. The detail names the recipient and the level that was refused.
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/auth-level-unavailable",
"title": "Authentication level not available",
"status": 422,
"instance": "/v1/...",
"docs_url": "https://docs.signenvoy.com/errors/auth-level-unavailable"
}