409 Conflict
Venue not ready to go live
- Code
venue_not_ready- Status
409Conflict- Type
https://errors.clavian.io/venue-not-ready
What it means
A venue in setup goes live only once its essential setup steps are done — opening hours set, a price players can pay, and a PC paired — and missingSteps lists the ones still missing. A venue already live or paused is not asked.
What to do
Show the steps missingSteps names, each with where it is done, and offer Go live again once they are. Read GET …/venues/{v}/setup for the whole list.
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/venue-not-ready",
"title": "Venue not ready to go live",
"status": 409,
"code": "venue_not_ready",
"requestId": "req_01k5znw4hmfay8vvr14d2pf2db"
}
Endpoints that return it
From the OpenAPI document, every endpoint that names it among its answers:
PATCH /v1/organizations/{organizationId}/venues/{venueId}Edit a venue