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 puts every BlitzAPI endpoint and the docs inside your AI tools, 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
The BlitzAPI MCP server gives Claude, Cursor or VS Code one tool per API endpoint, the documentation and built-in GTM skills. Ask for data in a chat, or have your assistant write the script that pulls it: same endpoints, same parameters, same responses.
Plug https://api.blitz-api.ai/mcp into Claude, Cursor, VS Code or any MCP-compatible tool, then sign in with your BlitzAPI account or send your API key.
Your assistant reads the actual API reference before it calls an endpoint, 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).
Your plan sets the rate, per endpoint: 10 requests per second on Start, 25 on Scale, a custom rate on Build Your Infra. Each endpoint has its own budget, so calls to different endpoints run in parallel without competing. Per-endpoint details and headers are listed in the API reference; the SDKs handle retries and backoff for you.
The MCP server connects your AI tool to BlitzAPI itself: one tool per endpoint to search and enrich people, companies and jobs, plus the docs. Blitz Skills package playbooks, scripts, prompts and workflows your agent runs on top of the API. Use the MCP server to pull data from a chat, and Skills to make a workflow repeatable.
Yes. https://docs.blitz-api.ai/mcp gives your AI tool the documentation only, with no account and no records used. The main server, https://api.blitz-api.ai/mcp, already includes the docs through its docs tools, so you don't need both.