Error reference / otp-invalid
That code isn't right
The one-time code entered does not match the one that was emailed.
| Problem type | /problems/otp-invalid |
|---|---|
| HTTP status | 422 |
| Emitted by | Signing page |
| Title values | That code isn't right |
| Trigger | Signing page: the one-time code does not match; carries `attempts_remaining` |
What happened
The code entered for the confirmation step did not match the latest code sent to the recipient. The response is HTTP 422 and carries attempts_remaining.
What it means
Codes are six digits and each send issues a new one; only the most recent code counts. After five wrong attempts the link stops working.
What to do next
Check the most recent email and enter the code again. If it keeps failing, request a new code from the signing page.
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/otp-invalid",
"title": "That code isn't right",
"status": 422,
"instance": "/v1/...",
"docs_url": "https://docs.signenvoy.com/errors/otp-invalid"
}