409 Conflict
The terms or privacy policy have changed
- Code
consent_version_outdated- Status
409Conflict- Type
https://errors.clavian.io/consent-version-outdated
What it means
The versions of the terms or the privacy policy the client showed are not the ones in force now.
What to do
Read the documents in force from GET /v1/meta, show them, and ask for acceptance again.
Example
The API answers with status 409 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-version-outdated",
"title": "The terms or privacy policy have changed",
"status": 409,
"code": "consent_version_outdated",
"requestId": "req_01k5znw4hmfay8vvr14d2pf2db"
}
Endpoints that return it
From the OpenAPI document, every endpoint that names it among its answers:
POST /v1/me/consentsAccept a new version of the terms or the privacy policyPOST /v1/station/sign-in/phoneSign a player in at a kiosk with a phone code