# campaign_lead_limit

> The campaign_lead_limit 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/campaign-lead-limit

The API returns `campaign_lead_limit` 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

- [Leads (Campaigns)](https://warmerly.com/docs/campaigns/leads)

## What the response looks like

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

- [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…
- [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.