503
Retry with backoffService unavailable — Your account settings could not be loaded just now, so the request was refused rather than served on a guess. Transient.
Response body
{ "error": { "code": "service_unavailable", … } }
Should you retry?
Yes — with exponential backoff, and honour Retry-After
when it is present.
What it means
Every request is served under your account's plan — its rate limits, the fields you have access to, and whether API access is on. When that plan cannot be read and no recent copy is at hand, the API refuses with service_unavailable instead of guessing, because a guess could apply the wrong limits or the wrong fields. It clears on its own within seconds. Retry-After and error.details.retry_after_seconds say how long to wait. The billing webhook (POST /v4/billing/stripe) can also answer 503 webhook_not_configured; that one is a standing configuration gap, not a blip, and only matters to operators.
Common causes
- A brief problem reading account settings on JobFront's side, usually just after a deploy.
- `webhook_not_configured` only: the Stripe billing webhook is not set up for this deployment.
How to fix it
Wait Retry-After seconds and send the same request again. If service_unavailable persists for more than a minute, send us the request_id. For webhook_not_configured, contact your JobFront representative — it will not clear by retrying.