Leads
List Leads
Retrieve leads for a campaign with optional filtering
GET
Documentation Index
Fetch the complete documentation index at: https://lupitor-docs.com/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint Alias: You can also use
/api/v1/records instead of /api/v1/leads. Both endpoints are functionally identical - use whichever naming convention fits your integration.Authentication
Your API key with
read or write scopeQuery Parameters
The ID of the campaign to list leads for
Filter leads by statusOptions:
raw- Never been calledattempting- Currently being calledexhausted- Max attempts reachedconcluded- Successfully completed
Maximum number of leads to return per request. Default:
1000, Max: 8000Pagination cursor from a previous response. Use this to fetch the next page of results.
Response
Whether the request was successful
Error message if request failed
Lead Status Lifecycle
Status Meanings:
- raw: Lead has never been called
- attempting: Lead is currently in the calling queue
- exhausted: Max call attempts reached without success
- concluded: Call completed successfully
Common Errors
| Error | Cause | Solution |
|---|---|---|
campaignId query parameter is required | Missing campaignId | Add campaignId to query string |
Invalid or inactive API key | Wrong API key | Check your API key |
Campaign not found or access denied | Wrong campaign or no access | Verify campaignId and API key scope |
Usage Tips
Pagination
This endpoint supports cursor-based pagination for handling large datasets efficiently.Limits:
- Default: 1,000 leads per request
- Maximum: 8,000 leads per request
cursor parameter to fetch additional pages.