Clearbit (HubSpot Breeze Intelligence) · Rate Limits

Clearbit Rate Limits

Clearbit documents a flat 600 requests per minute per API, explicitly excluding the Streaming and Reveal endpoints, and tells callers to read their live budget off the response headers rather than assume the number. The headers are real and were verified: every request to person/company/prospector.clearbit.com returns the legacy x-ratelimit-limit / x-ratelimit-remaining / x-ratelimit-reset triple, and returns it even on a 401, so an unauthenticated caller can observe the budget. Coverage is uneven — reveal, risk, discovery and the streaming host emit no rate-limit headers at all.

Clearbit Rate Limits is the machine-readable rate-limit profile for Clearbit (HubSpot Breeze Intelligence) on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 9 rate-limit definitions, measuring requests, concurrent-connections, and enrichments-per-list.

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

Tagged areas include Sales Intelligence, B2B, Enrichment, Reveal, and HubSpot.

9 Limits Throttle: 429
Sales IntelligenceB2BEnrichmentRevealHubSpotMarketingRate LimitingQuotasThrottling

Limits

Enrichment (Person / Company / Combined) api-key
requests
600
Documented 600/min. x-ratelimit-* triple confirmed live on both hosts.
Prospector api-key
requests
600
Name to Domain api-key
requests
600
Autocomplete (free, unauthenticated) ip
requests
600
Documented at 600/min alongside the other free APIs. No x-ratelimit-* headers on the 200 response; the host is CloudFront-fronted with a ~30 day cache-control, so repeat lookups are served from edge cache and may not reach the origin budget at all.
Risk api-key
requests
600
Documented at 600/min. No rate-limit headers observed on response.
Reveal api-key
requests
Explicitly excluded from the documented 600/min figure and no limit is published in its place. No rate-limit headers on the response either — the budget is neither documented nor observable.
Streaming Enrichment api-key
concurrent-connections
Explicitly excluded from the 600/min figure. Each request can hold a connection open for up to 60 seconds, so the meaningful constraint is concurrency, not request rate — and no concurrency limit is published.
Discovery api-key
requests
No published limit and no headers observed.
List Enrichment (platform feature) account
enrichments-per-list
3
"List Enrichment now limits enriching the same list to three times within an hour." Product feature, not an API endpoint. Announced 2024-04-16.

Policies

Read the headers, not the docs
Provider explicitly directs callers to the response headers for current status. Treat 600/min as the documented ceiling and x-ratelimit-limit as the operative one — the anonymous limit observed was 100, an order of magnitude below the documented figure.
Backoff
No Retry-After is sent. Sleep until x-ratelimit-reset (unix epoch seconds), then retry.
Failed requests count
401 responses decrement x-ratelimit-remaining. Retry loops against a bad credential will exhaust the budget.
Caching
Cache enrichment results where the terms allow; Clearbit itself caches and offers cached=true to force the cached response rather than a 202 queue.