Crunchbase · Rate Limits

Crunchbase Data Rate Limits

Crunchbase documents a single API-wide rate limit of 200 calls per minute across the Data API endpoints, applied to protect platform reliability and performance. Beyond the per-minute request cap, usage is governed by the terms of the account's license (Enterprise, Applications, or Basic) rather than by published per-endpoint quotas. Search responses are additionally bounded to 50 items by default and 1000 items maximum per request, with keyset pagination (after_id / before_id) used to traverse larger result sets.

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

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

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

Tagged areas include Company Data, Funding Data, Web Intelligence, Rate Limiting, and Quotas.

5 Limits Throttle: 429
Company DataFunding DataWeb IntelligenceRate LimitingQuotas

Limits

API Calls account
requests
200 per minute
Documented API-wide rate limit across all Data API endpoints.
Search Result Size request
items
50 default / 1000 max
Per-request result cap on POST /searches/{collection}; page with after_id / before_id.
Autocomplete Result Size request
items
25 max
The limit query parameter on GET /autocompletes maxes at 25.
Entity Card Inline Items request
items
100 per card
Cards included via card_ids return at most 100 items; use the card endpoint for more.
License Call Allowance account
requests
per contract
Total call volume is governed by the Enterprise / Applications / Basic license terms; not publicly published.

Policies

HTTPS Required
All API requests must use HTTPS; non-HTTPS requests are rejected with HTTP 426.
Keyset Pagination
Search and list endpoints use keyset cursors (after_id / before_id) so results stay stable as the dataset changes.
Backoff Strategy
Clients should stay under 200 calls/minute and implement exponential backoff with jitter, honoring Retry-After on 429 responses.

Sources