503 Service Unavailable
Busy, try again
- Code
service_unavailable- Status
503Service Unavailable- Type
https://errors.clavian.io/service-unavailable
What it means
The API is handling as much as it can at this moment and could not get to this request in time, so nothing it would have changed was kept.
What to do
Wait at least as long as the Retry-After header says, then send the same request again, with the same Idempotency-Key where the endpoint takes one.
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/service-unavailable",
"title": "Busy, try again",
"status": 503,
"code": "service_unavailable",
"requestId": "req_01k5znw4hmfay8vvr14d2pf2db"
}
Endpoints that return it
From the OpenAPI document, every endpoint that names it among its answers:
GET /v1/boot-server/configThe boot server’s signed config and licence leasePOST /v1/organizations/{organizationId}/venues/{venueId}/stations/{stationId}/lockLock or unlock a stationPOST /v1/organizations/{organizationId}/venues/{venueId}/stations/{stationId}/maintenancePut a station into or out of maintenancePOST /v1/organizations/{organizationId}/venues/{venueId}/stations/{stationId}/messageMessage a player at a stationPOST /v1/organizations/{organizationId}/venues/{venueId}/stations/{stationId}/powerPower a stationPOST /v1/organizations/{organizationId}/venues/{venueId}/stations/{stationId}/setup/skipSkip a station’s start-up setup