503 Service Unavailable
Codes cannot be sent right now
- Code
otp_delivery_unavailable- Status
503Service Unavailable- Type
https://errors.clavian.io/otp-delivery-unavailable
What it means
No provider could deliver the one-time code, because none is set up or every one that is failed. No code was sent.
What to do
Say that no code was sent, and let the person try again in a few minutes or sign in another way. Never tell them to wait for a message.
Example
The API answers with status 503 and this body, as application/problem+json. A detail may be added, saying what went wrong this time; it is for people, and changes.
{
"type": "https://errors.clavian.io/otp-delivery-unavailable",
"title": "Codes cannot be sent right now",
"status": 503,
"code": "otp_delivery_unavailable",
"requestId": "req_01k5znw4hmfay8vvr14d2pf2db"
}
Endpoints that return it
From the OpenAPI document, every endpoint that names it among its answers:
POST /v1/hq/organizations/{organizationId}/migrations/{migrationId}/moved-emailSend the "account moved" email to the run’s waiting playersPATCH /v1/meChange your own profile: marketing, and your email address or phone numberPOST /v1/organizations/{organizationId}/imported-players/{importedPlayerId}/claim/email-codeSend a code to the email a moved player is claiming with, at the counterPOST /v1/station/sign-in/email/codeSend a sign-in code to an email address, from a kioskPOST /v1/station/sign-in/phone/codeSend a sign-in code to a phone, from a kioskPOST /v1/station/sign-in/profileFinish a just-created account’s profile at the kiosk