# payment_required

> The payment_required 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/payment-required

The API returns `payment_required` 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`).

## Where the API reference mentions it

- [Quotas are not rate limits (Usage & limits)](https://warmerly.com/docs/usage/quotas-are-not-rate-limits)

## What the response looks like

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

- [conflict](https://warmerly.com/docs/errors/conflict): The conflict error from the Warmerly API (HTTP 409): The request conflicts with the resource's current state.
- [quota_exhausted](https://warmerly.com/docs/errors/quota-exhausted): The quota_exhausted error from the Warmerly API (HTTP 402): A plan limit or monthly allowance is used up…
- [plan_capacity](https://warmerly.com/docs/errors/plan-capacity): The plan_capacity error from the Warmerly API (HTTP 402): A plan limit or monthly allowance is used up (the…