List leads
Newest first by default. Page with `page` and `limit`, or for deep lists pass `cursor` (empty first, then `nextCursor`): cursor pages skip the count and stay fast. Without `cursor` matches are counted up to 10,000 unless `includeTotal=true`.
Newest first by default. Page with page and limit, or for deep lists pass cursor (empty first, then nextCursor): cursor pages skip the count and stay fast. Without cursor matches are counted up to 10,000 unless includeTotal=true.
X-API-Key<token>Create in the console: Settings → API & webhooks.
page?PagePage number, from 1. Ignored when cursor is sent.
1 <= value1limit?LimitItems per page, up to 200.
1 <= value <= 20025search?|Matches part of the name, phone, email, company, title or external id.
status?|Only leads with this pipeline status key (your workspace's statuses).
leadSourceId?|Only leads from this lead source.
campaignId?|Only leads in this campaign.
dateFilter?stringCreated since 00:00 UTC today (today), or since 00:00 UTC 7 days ago (week) or 30 days ago (month). all (or no value) applies no date filter.
"today""week""month""all"sortBy?string"createdAt""createdAt""name""status""lastContact""company""callStatus"sortOrder?string"desc""asc""desc"includeStats?IncludestatsAdd stats (total, byStatus, recentlyAdded, notCalled) for the filter.
falseincludeTotal?IncludetotalCount every match exactly. By default the count stops at 10,000 (pagination.totalCapped says when there are more).
falsecursor?|Empty for the first page, then the previous response's nextCursor. Only with the default sort (newest first); skips the count.
assignedTo?|me, unassigned, or a team member's user ID.
tag?|Only leads with this tag.
OK
application/json- response
One page of leads.
hasMore?|True when another page follows.
leads*array<>Leads on this page.
nextCursor?|Pass as cursor for the next page. Only with the default sort (newest first).
pagination?|Page position and totals.
stats?|With includeStats=true: total, byStatus, recentlyAdded and notCalled for the filter.
success?SuccessAlways true on a 2xx response.
true[key: string]?anycurl -X GET 'https://api.callmitra.ai/api/v1/leads/'{ "hasMore": false, "leads": [ { "attributes": { "city": "Pune" }, "callAttempts": 0, "callStatus": "not_called", "campaignIds": [], "campaignNames": [], "company": "Rao Traders", "createdAt": "2026-11-15T10:00:00+00:00", "dncOptOut": false, "email": "[email protected]", "id": "6f1c2a9e-3b7d-4c55-9a0e-1d2f3a4b5c6d", "name": "Asha Rao", "phone": "+919876543210", "source": "website", "status": "new", "tags": [], "title": "Owner", "updatedAt": "2026-11-15T10:00:00+00:00" } ], "pagination": { "currentPage": 1, "hasNextPage": false, "hasPreviousPage": false, "itemsPerPage": 25, "totalCapped": false, "totalItems": 1, "totalPages": 1 }, "success": true}List custom lead fields GET
Every custom field defined in the workspace. Send values for these keys in a lead's `attributes` object on createLead and updateLead; pushLead takes them as top-level fields. `valueType` says how they are stored and compared in audience rules.
Update a lead PUT
Changes only the fields you send. Send `If-Match` with the lead's `updatedAt` to refuse the write (`lead_changed`) when someone changed the lead after you read it. A new `phone` is stored in E.164 form like on create. Campaign IDs you cannot access are skipped.