# service_unavailable

> The service_unavailable error from the Warmerly API (HTTP 503): A feature or an upstream service is not available right now.

Source: https://warmerly.com/docs/errors/service-unavailable

The API returns `service_unavailable` with HTTP status **503**.

A feature or an upstream service is not available right now.

## What the response looks like

```json
{
  "error": {
    "code": "service_unavailable",
    "message": "...",
    "details": null
  }
}
```

`error.code` is stable and safe to branch on. `error.message` is debugging context, not something to parse. The full list of codes, and the rate limits, are on [Errors & Rate Limits](https://warmerly.com/docs/errors).

## More from Errors & Rate Limits

- [billing_locked](https://warmerly.com/docs/errors/billing-locked): The billing_locked error from the Warmerly API (HTTP 402): A plan limit or monthly allowance is used up (the…
- [too_many_requests](https://warmerly.com/docs/errors/too-many-requests): The too_many_requests error from the Warmerly API (HTTP 429): Rate limit exceeded, see below.
- [internal_error](https://warmerly.com/docs/errors/internal-error): The internal_error error from the Warmerly API (HTTP 500): Something went wrong on Warmerly's end.