400 Bad Request

Accept the terms and the privacy policy

Code

consent_required

Status

400 Bad Request

Type

https://errors.clavian.io/consent-required

What it means

The request needs documents the person has not accepted: the terms and the privacy policy for an account made at sign-in, or the privacy policy for switching marketing on. At sign-in, the code that checked out is kept.

What to do

Show the documents in force, listed by GET /v1/meta, and ask the person to accept them. At sign-in, send the same code again with the acceptance.

Example

The API answers with status 400 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/consent-required",
  "title": "Accept the terms and the privacy policy",
  "status": 400,
  "code": "consent_required",
  "requestId": "req_01k5znw4hmfay8vvr14d2pf2db"
}

Endpoints that return it

From the OpenAPI document, every endpoint that names it among its answers:

• PATCH /v1/meChange your own profile: marketing, and your email address or phone number
• PUT /v1/notifications/prefsChange your notification preferences
• POST /v1/station/sign-in/phoneSign a player in at a kiosk with a phone code