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.

Coresignal Rate Limits is the machine-readable rate-limit profile for Coresignal on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 7 rate-limit definitions, measuring requests_per_second, requests_per_minute, urls_per_minute, and credits.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and quotaExceeded.

Tagged areas include Agentic Search, B2B Data, Companies, Data as a Service, and Employees.

7 Limits Throttle: 429 Quota: 429
Agentic SearchB2B DataCompaniesData as a ServiceEmployeesJob PostingsRate LimitingQuotasThrottling

Limits

Collect (GET) requests api-key
requests_per_second · second
54
Applies across most APIs (Company, Employee, Jobs Collect endpoints).
Search (POST) and Enrich (GET) requests api-key
requests_per_second · second
18
Applies to most Company and Employee Search/Enrich endpoints.
Bulk Collect operations api-key
requests_per_second · second
27
Applies to Bulk Collect across Company, Employee, and Jobs APIs.
Clean Employee API (subscription) api-key
requests_per_minute · minute
9
Base Employee API (subscription) api-key
requests_per_minute · minute
18
Real-time Employee API api-key
urls_per_minute · minute
50
Measured in URLs submitted per minute rather than HTTP calls.
Plan credit allotment account
credits
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.

Sources