REST API
Simple, predictable v2 endpoints authenticated with an x-api-key header. Search, enrich, validate, and activate from any language.
One REST API, typed SDKs for Python and TypeScript, an MCP server for your AI tools, and composable GTM skills for agents. Ship your first workflow in minutes.
DEVELOPER TOOLKIT












Whether you write the code, your team does, or your agent does, BlitzAPI meets you where you build.
Simple, predictable v2 endpoints authenticated with an x-api-key header. Search, enrich, validate, and activate from any language.
Fully typed Python and TypeScript clients with auto-pagination, automatic retries, and client-side rate limiting built in.
An MCP server that feeds your AI tools live documentation, and Blitz Skills that package entire GTM playbooks for coding agents.
First call
A LinkedIn profile URL in, a verified work email out. Same endpoint, same parameters, same response. You pick the interface, not the API.
curl -X POST https://api.blitz-api.ai/v2/enrichment/email \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"person_linkedin_url":"https://www.linkedin.com/in/example-person"}'from blitz_api import BlitzAPI
client = BlitzAPI() # reads BLITZ_API_KEY
email = client.enrichment.email(
person_linkedin_url="https://www.linkedin.com/in/example-person"
)
if email.found:
print(email.email)import { BlitzAPI } from "blitz-api-js";
const client = new BlitzAPI(); // reads BLITZ_API_KEY
const email = await client.enrichment.email({
person_linkedin_url: "https://www.linkedin.com/in/example-person",
});
if (email.found) console.log(email.email);foundemailall_emails[]Sign up, grab your key, and send it in the x-api-key header on every request. Keep it server-side, never in client code.
pip install blitz-api-py or npm install blitz-api-js. Both read BLITZ_API_KEY from your environment and expose the same namespaces.
Turn a LinkedIn profile URL into a verified work email in a few lines, or run your first people search with typed, autocompleted filters.
Auto-pagination, retries with backoff on 429 and 5xx, and client-side rate limiting keep your batch jobs inside your limits.
AI-native tooling
Every page of docs.blitz-api.ai is available as Markdown and indexed for the MCP server. Whether you write the code or your agent does, it works from the same source of truth: real endpoints, current parameter schemas, accurate response shapes.
Plug https://docs.blitz-api.ai/mcp into Claude, Cursor, or any MCP-compatible tool.
Your assistant reads the actual API reference instead of guessing endpoints and parameter names.
The endpoints you'll call first.
Every request carries your key in the x-api-key header. The SDKs read it from the BLITZ_API_KEY environment variable. Always call BlitzAPI from your backend, never expose the key in browsers or mobile apps.
The REST API works from any language. Official SDKs cover Python (blitz-api-py, Python 3.10+) and TypeScript/JavaScript (blitz-api-js, Node 20+ or any runtime with global fetch).
During the lifetime offer, every account runs at 50 requests per second, and keeps that rate for as long as the subscription stays active. Per-endpoint details and headers are listed in the API reference; the SDKs handle retries and backoff for you.
The MCP server gives your AI tool live read access to the docs so it writes correct API code. Skills go further: they package ready-to-run playbooks, scripts, prompts, and workflows your agent can execute. They complement each other.