The Companies API · Rate Limits

Thecompaniesapi Rate Limits

The Companies API applies two independent controls. First, a per-second request rate limit (RPS) that is tied to the subscription plan - Startup 50 RPS, Scaleup 250 RPS, Enterprise 1,000 RPS. Second, a monthly credit allowance that meters how much work an account can perform; each call spends credits and, once the included allowance is exhausted, overage credits are billed per 1,000. Long-running and bulk workloads are dispatched through the asynchronous Actions job queue so they do not have to be issued as a burst of synchronous requests.

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

It captures 5 rate-limit definitions, measuring requests and credits.

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

Tagged areas include Company Data, Data Enrichment, Firmographics, Rate Limiting, and Quotas.

5 Limits Throttle: 429
Company DataData EnrichmentFirmographicsRate LimitingQuotasThrottling

Limits

Requests Per Second (Startup) account
requests
50/sec
Per-plan synchronous request rate limit on the Startup tier.
Requests Per Second (Scaleup) account
requests
250/sec
Per-plan synchronous request rate limit on the Scaleup tier.
Requests Per Second (Enterprise) account
requests
1000/sec
Per-plan synchronous request rate limit on the Enterprise tier.
Monthly Credit Allowance account
credits
per plan (50k / 250k / 500k)
Each call spends credits; overage billed per 1,000 credits once the allowance is used.
Free Signup Credits account
credits
500 (one-time)
Granted to new accounts for evaluation, no credit card required.

Policies

Credit Metering
Work is metered in credits rather than by a flat request quota; different operations can cost different amounts of credits.
Asynchronous Actions
Bulk and long-running jobs run through the Actions queue (POST /v2/actions) and are polled over REST, smoothing demand against the per-second limit.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources