# Rate limits & errors

> GET /leads/search has its own throttle on top of your API key's per-minute limit: 120 requests per 5 minutes, per user (not per key or IP), and GET…

Source: https://warmerly.com/docs/leads/rate-limits-and-errors

`GET /leads/search` has its own throttle on top of your API key's per-minute limit: **120 requests per 5 minutes, per user** (not per key or IP), and `GET /leads/count` has the same limit on its own counter. Exceeding either returns `429 too_many_requests`. See [Errors & Rate Limits](https://warmerly.com/docs/errors) for the shared error envelope and your key's general per-minute limit.

## More from Leads

- [Push to a campaign](https://warmerly.com/docs/leads/push-to-a-campaign): Same selection shape as export, plus a target campaign. It adds matching companies directly to a campaign's…
- [LinkedIn people search](https://warmerly.com/docs/leads/linkedin-people-search): A different database to the company search above: this queries LinkedIn through your own connected LinkedIn…
- [Export quota](https://warmerly.com/docs/leads/export-quota): Returns your current lead-export usage for the billing period. A pure read, checking it never debits quota.