๐ Endpoint Index
Base URL:https://api.blitz-api.ai. All endpoints use POST except key-info.
Waterfall ICP, Employee Finder, Search Company Jobs, Company Enrichment, LinkedIn URL to Domain and the two company distribution endpoints take a Company LinkedIn URL as input (not a domain). If you only have a domain, use
/v2/enrichment/domain-to-linkedin first.๐ Country Codes
All BlitzAPI search endpoints use 2-letter country codes following the ISO 3166-1 alpha-2 standard. Letter case does not matter, andUK is read as GB. A value of any other length (e.g., USA instead of US) returns a 422. See the Field Normalization reference for the full list and the rules.
Common Country Codes List
Common Country Codes List
๐ง Email Logic: Matching vs. Guessing
A common misconception is that enrichment APIs โguessโ emails (permutations likefirst.last@domain.com). BlitzAPI does not do this.
How we work
- Identity Matching: We match the LinkedIn profile against a massive dataset of known, verified identities.
- No Permutations: We only return an email if we have a concrete record of it linked to that specific individual.
- Freshness Guarantee:
- We do not serve stale data.
- Every email in our database is re-validated at least once every 30 days.
- If an email bounces during a re-validation, it is immediately removed from circulation.
๐ฆ Rate Limits & Latency
To ensure stability for all users:- Rate limit: Your requests-per-second (RPS) limit depends on your plan and applies per endpoint. Each endpoint has its own independent budget, so calls to
/enrichment/emailand/enrichment/phonedonโt compete. Use themax_requests_per_secondsfield from/v2/account/key-infoto get your exact per-endpoint limit. It is counted per account: all API keys of your account share each endpointโs budget. - Burst: Nothing is queued. Requests are counted over a sliding 1-second window, and any request above the limit returns
429 Too Many Requestsat once. - Retry on 429: The
429carriesRetry-After: 1, so waiting 1 second is enough. Client-side rate limiting should prevent this.
Error Codes:
Every response, errors included, carries an
X-Request-Id header: quote it when you contact support. Every JSON error body also carries fair_usage, with the same id in fair_usage.request_id.
See Errors for the 422 response format and the fair_usage block of an error.
๐ฆ Response Compression
Send anAccept-Encoding header to get a compressed JSON response. The API supports gzip, br and zstd.
- The q-values of the header decide the encoding. On a tie,
gzipwins:Accept-Encoding: gzip, br, zstdreturnsgzip. - A small response is sent uncompressed.
- A request without the header gets the plain body.
Content-Encoding response header names the encoding of the body. Most HTTP clients send Accept-Encoding and decompress the body automatically.
