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 feeds your AI tools live documentation, 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

Docs your AI tools can read

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.

MCP server URL

Plug https://docs.blitz-api.ai/mcp into Claude, Cursor, or any MCP-compatible tool.

Fewer hallucinations

Your assistant reads the actual API reference instead of guessing endpoints and parameter names.

DOCS → YOUR AI TOOLSLIVE
$ curl docs.blitz-api.ai/mcpHTTP 200 · application/json
REAL ENDPOINTS · CURRENT SCHEMAS

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: "antoine@…"}

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?

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.

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

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.

Data shouldn't be
the problem

Grab. Connect. Build.