Header format
Authorization: Bearer pl_demo_publicLeads Pro reference
Everything the first API customer needs to test the product.
The public docs stay intentionally practical: clear authentication, stable endpoint shapes, useful examples, and the exact failure modes users need before they build against the API.
Base configuration
Base URLhttps://leads-pro.co/api
AuthenticationBearer API key
Sandbox keypl_demo_public
Product surfaceenrich, batch, search, keys, usage
Authentication
Use a standard bearer token header.
Demo mode ships with a public sandbox key. Production customers should create a scoped key per workspace and rotate keys through the dashboard.
Content type
Content-Type: application/jsonKey management
Generate and revoke keys in the workspace dashboard, then pass them as `Authorization` or `x-api-key`.
Available endpoints
The backend is live, not mocked.
The current public deployment supports health checks, single enrich, batch enrich, people search, company search, and usage metadata.
GET /api/health
Service health, version, feature flags, and dataset metadata.
POST /api/v1/enrich
Single lookup by email, phone, LinkedIn slug, or name plus company/domain.
POST /api/v1/enrich/batch
Batch lookup for arrays of records with per-item success or error results.
POST /api/v1/search/people
Search profiles by title, seniority, company, geography, skills, and keywords.
POST /api/v1/search/companies
Search companies by domain, industry, headcount, technology, geography, and status.
GET /api/v1/me + /api/v1/usage
Inspect workspace plan, key metadata, monthly credits, and rate limit usage.
Single enrichment example
curl -X POST https://leads-pro.co/api/v1/enrich \
-H "Authorization: Bearer pl_demo_public" \
-H "Content-Type: application/json" \
-d '{
"email": "amanda@northpeak.io",
"company": "North Peak"
}'Batch enrichment example
curl -X POST https://leads-pro.co/api/v1/enrich/batch \
-H "Authorization: Bearer pl_demo_public" \
-H "Content-Type: application/json" \
-d '{
"items": [
{ "email": "amanda@northpeak.io" },
{ "phone": "+1 415 555 0106" },
{ "linkedin": "priya-shah-growth" }
]
}'Search examples
curl -X POST https://leads-pro.co/api/v1/search/people \
-H "Authorization: Bearer pl_demo_public" \
-H "Content-Type: application/json" \
-d '{"job_title":"Revenue Operations","country":"United States","limit":5}'
curl -X POST https://leads-pro.co/api/v1/search/companies \
-H "Authorization: Bearer pl_demo_public" \
-H "Content-Type: application/json" \
-d '{"technology":"AWS","country":"United States","status":"verified"}'Response model
Stable fields that are usable inside downstream systems.
The API returns a predictable structure for person, company, and meta fields so you can wire it into CRM, automation, or agent workflows without brittle parsing.
FieldTypeDescription
`person.full_name`stringNormalized full name of the matched contact.
`person.job_title`stringCurrent title when available, plus department and management level.
`company.*`objectIndustry, domain, headcount, website, technologies, location, and status.
`meta.request_id`stringRequest identifier for support, audit, and history correlation.
`meta.credits_used`integerCredits consumed by the request for quota and billing logic.
Errors
Failure modes should be obvious, not mysterious.
HTTPCodeDescription
400
invalid_requestMissing or invalid parameters401
unauthorizedMissing or invalid API key403
quota_exceededMonthly credit limit reached403
batch_not_availableBatch access is not enabled on the current plan404
no_matchNo enrichment record matched the input429
rate_limitedRate limit exceeded for the current keyUse OpenAPI or the skill docs with agent platforms.
Import `/openapi.json` into GPTs, Dify, Coze, or custom agents, or use the skill markdown files from the dashboard API keys page.
Use the docs to validate shape, then switch to the workspace.
The dashboard adds API key creation, history, search, batch tools, and CSV-based enrichment workflows for day-to-day usage.