Skip to main content
Agents & LLMs: a Markdown version of this page is available by appending .md to the URL, and the full documentation index is at llms.txt.
This reference lists every BlitzAPI v2 endpoint at a glance, with its HTTP method and what it takes and returns, then the standards shared across endpoints: 2-letter country codes, how email matching works, rate limits per endpoint, recommended timeouts and error codes. Use it to pick the right endpoint and build reliable integrations.

๐Ÿ“‹ 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, and UK 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.
To search globally, leave the country filter out. You can also send "WORLD" in the codes to keep on Find People, TAM By People, Company Search, Waterfall ICP and Employee Finder (where it is the default): it turns the country filter off. The job endpoints and the exclude lists do not accept "WORLD".
For the full list of codes, see the ISO 3166-1 alpha-2 list.

๐Ÿ“ง Email Logic: Matching vs. Guessing

A common misconception is that enrichment APIs โ€œguessโ€ emails (permutations like first.last@domain.com). BlitzAPI does not do this.

How we work

  1. Identity Matching: We match the LinkedIn profile against a massive dataset of known, verified identities.
  2. No Permutations: We only return an email if we have a concrete record of it linked to that specific individual.
  3. 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.
This approach ensures a significantly lower bounce rate compared to โ€œpattern-matchingโ€ tools.

๐Ÿšฆ 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/email and /enrichment/phone donโ€™t compete. Use the max_requests_per_seconds field from /v2/account/key-info to 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 Requests at once.
  • Retry on 429: The 429 carries Retry-After: 1, so waiting 1 second is enough. Client-side rate limiting should prevent this.
Recommended Client Timeouts: 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 an Accept-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, gzip wins: Accept-Encoding: gzip, br, zstd returns gzip.
  • A small response is sent uncompressed.
  • A request without the header gets the plain body.
The Content-Encoding response header names the encoding of the body. Most HTTP clients send Accept-Encoding and decompress the body automatically.