422 Unprocessable Content

Profile incomplete

Code

profile_incomplete

Status

422 Unprocessable Content

Type

https://errors.clavian.io/profile-incomplete

What it means

The venue needs profile fields the player has not filled in, such as a verified phone number, before a session can start.

What to do

Ask the player for the missing fields, as the kiosk’s short form does, save them, and start the session again.

Example

The API answers with status 422 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/profile-incomplete",
  "title": "Profile incomplete",
  "status": 422,
  "code": "profile_incomplete",
  "requestId": "req_01k5znw4hmfay8vvr14d2pf2db"
}

Endpoints that return it

No endpoint in the OpenAPI document names it yet. It is part of the contract already, so a client can handle it before an endpoint sends it.