Developers

The developer toolkit for B2B data

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.

WORKFLOWDEVELOPER TOOLKIT
LIVEBLITZ API · V2

One API, every surface

Whether you write the code, your team does, or your agent does, BlitzAPI meets you where you build.

REST API

Simple, predictable v2 endpoints authenticated with an x-api-key header. Search, enrich, validate, and activate from any language.

Official SDKs

Fully typed Python and TypeScript clients with auto-pagination, automatic retries, and client-side rate limiting built in.

AI-native tooling

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

The same call, three ways

A LinkedIn profile URL in, a verified work email out. Same endpoint, same parameters, same response. You pick the interface, not the API.

POST/v2/enrichment/email
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);
200 OKfoundemailall_emails[]

From key to first result

  1. Get your API key

    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.

  2. Install an SDK

    pip install blitz-api-py or npm install blitz-api-js. Both read BLITZ_API_KEY from your environment and expose the same namespaces.

  3. Make your first call

    Turn a LinkedIn profile URL into a verified work email in a few lines, or run your first people search with typed, autocompleted filters.

  4. Scale it up

    Auto-pagination, retries with backoff on 429 and 5xx, and client-side rate limiting keep your batch jobs inside your limits.

AI-native tooling

BlitzAPI inside your AI tools

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.

MCP server URL

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.

Fewer hallucinations

Your assistant reads the actual API reference before it calls an endpoint, instead of guessing endpoints and parameter names.

BLITZAPI → YOUR AI TOOLSLIVE
HTTP 200$ curl -X POSTapi.blitz-api.ai/mcp
ONE TOOL PER ENDPOINT · DOCS · SKILLS

Where to go next

The endpoints you'll call first.

DEVELOPER TOOLKIT

One key, one base URL, one response shape, whether you call it with cURL, an SDK, or an agent.

API Docs
{"found": true,"email": "maya@acme.com"}

Frequently asked questions

How do I authenticate?

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.

Which languages are supported?

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).

How are rate limits handled?

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.

What is the difference between the MCP server and Blitz Skills?

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.

Is there a docs-only MCP server?

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.

Data shouldn't be
the problem

Grab. Connect. Build.