Developer API
Programmatic access to the Clapleads Atlas corpus — company prospecting, lookalikes, decision-makers, signals, enrichment, filter discovery, and MCP JSON-RPC. Authenticated with scoped API keys, metered per plan.
What you can do
Every endpoint below is live and documented in the Swagger UI. No roadmap items, no invented capabilities.
Company prospecting
Search 1.9B+ company records by name, location, industry, size, and more with structured filters.
POST /api/v3/prospecting/companies/People prospecting
Search stored contacts by role, seniority, department, and location (safe-mode aware).
POST /api/v3/prospecting/people/Lookalikes
Find companies or people similar to a seed profile — industry, size, and location matching.
POST /api/v3/lookalike/companies/Decision-makers
Discover key contacts at a specific company, ranked by seniority.
POST /api/v3/decision-makers/Signals
List stored company signals — hiring, funding, technology changes, and other intent events.
GET /api/v3/signals/Enrichment
Match an identifier to a person, then spend credits to reveal a specific field (email, phone).
POST /api/v3/enrich/match/Filter discovery
Enumerate the available search filters and their option values for companies and people.
GET /api/v3/filter-discovery/MCP JSON-RPC
MCP endpoint speaking JSON-RPC 2.0 for AI agents — tools/list, tools/call, and initialize.
POST /api/mcp/Authentication
Every API request is authenticated with an API key. Pass it in the X-API-Key header (industry-standard) or as Authorization: ApiKey <key>. Keys are created in-product and carry a scope that limits what they can do.
Scopes
An empty scope list means unrestricted (full access). A non-empty list restricts the key to the listed scopes — use this for least-privilege keys.
readSafe methods (GET/HEAD/OPTIONS). Also satisfies POST-based read endpoints like search.
writeMutating methods (POST/PUT/PATCH/DELETE). Use for creating or modifying records.
enrichCapability scope for the credit-spending enrich API (/api/v3/enrich/*). Grant only to keys that need it.
Keys are created and managed in the developer dashboard (requires an account). You can set an expiry, rotate keys, and revoke them at any time.
Rate limits & quotas
API calls are metered per plan. Each v3 endpoint carries a scoped rate limit (e.g. search, v3-enrich, api_meta) to prevent abuse. The exact rates are configured server-side and visible in the developer dashboard.
We link to the live rate table rather than copying numbers here — stale docs are dishonest docs. Check the in-product usage page for your current quota and consumption.
Live reference
The Swagger UI and OpenAPI schema are public by design — no account needed to read them.
Start building
Create a free account, generate an API key, and make your first request in minutes.