unavailable

HTTP status

503

Title

Service unavailable

Code

unavailable

What it means

The service, or a dependency it needs for this request, is unavailable for the moment.

It is also the catch-all of status 503: an error of that status that has no more specific code answers with this one.

What to do

Retry with backoff, honouring Retry-After when it is sent.

Example

Errors are RFC 9457 problem details, sent as application/problem+json. See Errors for every field.

{
  "type": "https://docs.furniops.com/errors/unavailable",
  "title": "Service unavailable",
  "status": 503,
  "code": "unavailable",
  "detail": "An explanation of this occurrence.",
  "request_id": "req_…",
  "doc_url": "https://docs.furniops.com/errors/unavailable"
}

Operations that answer it

• POST /v1/assistant/conversations/{conversation}/turns
• POST /v1/billing/card
• POST /v1/billing/credits/purchases
• POST /v1/billing/credits/purchases/preview
• PATCH /v1/billing/details
• GET /v1/billing/invoices
• POST /v1/billing/preview
• POST /v1/billing/subscription
• POST /v1/billing/subscription/cancel
• POST /v1/billing/subscription/resume
• POST /v1/billing/subscription/scheduled-change/cancel
• GET /v1/changes
• POST /v1/exports
• POST /v1/match-pairs/{id}/dismiss
• POST /v1/match-pairs/{id}/merge
• POST /v1/match-pairs/{id}/reopen
• GET /v1/matching/judge-settings
• PATCH /v1/matching/judge-settings
• POST /v1/merges/{id}/undo
• POST /v1/proposals/{id}/accept
• POST /v1/sources
• POST /v1/sources/{id}/uploads
• GET /v1/stream
• POST /v1/uploads/{id}/complete