Coresignal · Rate Limits
Coresignal Rate Limits
Coresignal publishes per-API rate limits expressed in requests per second (or per minute for subscription endpoints). Limits are scoped to the API key and differ by request type - Collect (GET) requests get the highest budget, Search (POST) and Enrich (GET) requests are throttled tighter, and Bulk Collect sits between them. Subscription endpoints (Real-time and Clean Employee API) use per-minute budgets. Monthly credit allotments are governed by the plan and act as quotas, not as short-window throttles.
7 Limits
Throttle: 429
Quota: 429
Agentic SearchB2B DataCompaniesData as a ServiceEmployeesJob PostingsRate LimitingQuotasThrottling
Limits
Collect (GET) requests api-key
54
Applies across most APIs (Company, Employee, Jobs Collect endpoints).
Search (POST) and Enrich (GET) requests api-key
18
Applies to most Company and Employee Search/Enrich endpoints.
Bulk Collect operations api-key
27
Applies to Bulk Collect across Company, Employee, and Jobs APIs.
Clean Employee API (subscription) api-key
9
Base Employee API (subscription) api-key
18
Real-time Employee API api-key
50
Measured in URLs submitted per minute rather than HTTP calls.
Plan credit allotment account
see plan tier
Monthly Collect and Search credits are governed by the subscribed plan (Starter / Pro / Premium). Treat as a quota, not a per-second throttle.
Policies
Per-API-key scoping
Rate limits are enforced per API key. Multi-tenant consumers should issue separate keys per environment or downstream tenant for isolation.
Backoff Strategy
On 429 responses, back off and retry; the documented per-second limits are short-window, so even a 1-2 second pause typically clears the throttle.
Credits vs throttling
Hitting the monthly credit cap blocks further calls until renewal or top-up; this is separate from per-second request throttling.
Bulk vs single-record
For bulk-style ingest, prefer Bulk Collect (27 rps) over multiple single-record Collect calls to maximize throughput within the published budget.