# billing_locked

> The billing_locked error from the Warmerly API (HTTP 402): A plan limit or monthly allowance is used up (the code varies by endpoint), or the workspace's…

Source: https://warmerly.com/docs/errors/billing-locked

The API returns `billing_locked` with HTTP status **402**.

A plan limit or monthly allowance is used up (the code varies by endpoint), or the workspace's billing needs attention (`billing_locked`).

## What the response looks like

```json
{
  "error": {
    "code": "billing_locked",
    "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

- [campaign_lead_limit](https://warmerly.com/docs/errors/campaign-lead-limit): The campaign_lead_limit error from the Warmerly API (HTTP 402): A plan limit or monthly allowance is used up…
- [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.
- [service_unavailable](https://warmerly.com/docs/errors/service-unavailable): The service_unavailable error from the Warmerly API (HTTP 503): A feature or an upstream service is not…