For AI agents: markdown of this page — /docs-content-en/entities/leads/list.md documentation index — /llms.txt
List leads
GET /v1/leads
Returns a list of leads with support for filtering, sorting and auto-pagination.
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
limit |
number | 50 |
Number of records (up to 5000). When limit > 50, auto-pagination is applied |
offset |
number | 0 |
Skip N records. When offset > 0, limit <= 500 is recommended |
select |
string | — | Field selection: ?select=id,title,stageId,amount. Unknown fields are ignored |
order |
object | — | Sorting: ?order[createdTime]=desc. Sort field names come from GET /v1/leads/fields |
filter |
object | — | Filter by fields from GET /v1/leads/fields.Filtering syntax. Example: ?filter[stageId]=NEW |
Examples
curl — personal key
curl "https://vibecode.bitrix24.com/v1/leads?limit=10&filter[stageId]=NEW&select=id,title,stageId,amount" \
-H "X-Api-Key: YOUR_API_KEY"
curl — OAuth application
curl "https://vibecode.bitrix24.com/v1/leads?limit=10&filter[stageId]=NEW&select=id,title,stageId,amount" \
-H "X-Api-Key: YOUR_APP_KEY" \
-H "Authorization: Bearer USER_SESSION_TOKEN"
JavaScript — personal key
const res = await fetch('https://vibecode.bitrix24.com/v1/leads?limit=10&filter[stageId]=NEW&select=id,title,stageId,amount', {
headers: {
'X-Api-Key': 'YOUR_API_KEY',
},
})
const { success, data, meta } = await res.json()
console.log(`Found ${meta.total} leads`)
JavaScript — OAuth application
const res = await fetch('https://vibecode.bitrix24.com/v1/leads?limit=10&filter[stageId]=NEW&select=id,title,stageId,amount', {
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
},
})
const { success, data, meta } = await res.json()
Response fields
| Field | Type | Description |
|---|---|---|
data |
array | Array of leads (fields — see Fields) |
meta.total |
number | Total number of records |
meta.hasMore |
boolean | More records available |
The card URL of any lead from the data array is built from its id:
https://<portal>.bitrix24.com/crm/lead/details/<id>/
<portal> — the Bitrix24 account domain. Access is restricted by the employee's permissions in Bitrix24.
Response example
{
"success": true,
"data": [
{
"id": 42,
"title": "Website request #42",
"name": "John",
"lastName": "Smith",
"stageId": "NEW",
"opportunity": 150000,
"currencyId": "USD",
"assignedById": 1,
"sourceId": "WEB",
"createdTime": "2026-04-10T14:30:00+00:00"
}
],
"meta": {
"total": 834,
"hasMore": true
}
}
Error response example
403 — no scope:
{
"success": false,
"error": {
"code": "SCOPE_DENIED",
"message": "This endpoint requires 'crm' scope"
}
}
Errors
| HTTP | Code | Description |
|---|---|---|
| 403 | SCOPE_DENIED |
The API key does not have the crm scope |
| 401 | TOKEN_MISSING |
The API key has no configured tokens |
Full list of common API errors — Errors.
Known specifics
The phone filter is not suitable for every search. A value without an operator is compared against the whole stored string: a lead whose number is stored as +1 (202) 555-0123 matches that exact string, but not 12025550123, because the plus sign, spaces, parentheses, and hyphens are part of the value. The filter also checks only the first number stored on a record: if both a work number and a mobile number are stored, searching by the mobile one returns an empty list. To find a lead by phone number in any format and by any of its numbers, use Duplicate search.
Auto-pagination: when limit > 50, Vibecode automatically requests multiple pages.
When to use search: for compound conditions, use POST /v1/leads/search — parameters are passed in the request body. See Search leads.