How is Leads different from Person Search?
Leads is optimized for prospect generation from a target description. Person Search is a more general people search endpoint with explicit filters.
Generate qualified lead/prospect candidates from a natural-language search_description (10-2000 chars). The request is queued and returns a request_id; poll the status endpoint or supply a callback_url for delivery.
Manual credentials take precedence over your account key.
The Leads API turns a target description into qualified person candidates for sales prospecting, growth campaigns, and outbound workflows.
This endpoint is asynchronous. A successful submit returns a request_id while the job runs in the background. Poll the same path with a GET request - same authentication headers - passing the request_id as a
query parameter:
Each poll returns the job's current status; once it is completed the payload carries the result shown under Responses. Polling an
unknown or expired request_id returns 404 request_not_found.
| Status | Meaning |
|---|---|
| queued · processing · pending | The job is still running - keep polling. |
| completed | The job finished; the payload carries the result and completed: true. |
| failed | Terminal - the job could not complete; the error field explains why. |
Poll every few seconds at first, backing off for long-running jobs. Polling is free - status checks never burn credits.
callback_url parameter and the completed payload is POSTed to your endpoint
when the job finishes - no polling required. Delivery is retried up to 5 times with exponential backoff (1s,
5s, 15s, 1m, 5m) and a 30-second timeout per attempt; respond with a 2xx status to acknowledge receipt.Credits are charged based on the matched configuration. The listed cost is the per-result unit price.
| Feature | Credits | Notes |
|---|---|---|
| Lead Search | 1 | Charged on successful lead searches |
| No results | 0 | Empty results never burn credits |
A successful response wraps the payload in the { success, data, timestamp } envelope (also shown live in the panel on the right):
{
"success": true,
"data": {
"request_id": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4_1717000000_4271",
"status": "completed",
"completed": true,
"result": [
{
"platform": "linkedin",
"post_url": "https://linkedin.com/feed/update/urn:li:activity:987654",
"post_content": "Just launched our new onboarding flow - 40% faster time-to-value.",
"post_date": "2026-01-14T14:22:00Z",
"author": {
"name": "Jane Doe",
"username": "janedoe",
"profile_url": "https://linkedin.com/in/janedoe",
"headline": "Head of Marketing at Acme",
"image_url": "https://cdn.example.com/avatars/janedoe.jpg"
},
"engagement": {
"likes": 245,
"comments": 18,
"shares": 12
}
}
],
"completed_on": "2026-01-15T10:35:00Z"
},
"timestamp": "2026-01-01T00:00:00"
}