For AI agents: markdown of this page — /docs-content-en/entities/companies/list.md documentation index — /llms.txt
List companies
GET /v1/companies
Returns a list of companies with filtering, sorting and auto-pagination.
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
limit |
number | 50 |
Number of records (up to 5000) |
offset |
number | 0 |
Skip N records. For a full-collection walk a cursor is cheaper — order[id]=asc plus filter[>id] from meta.nextAfterId |
select |
string | — | Field selection: ?select=id,title,phone,industry |
sort |
string | — | Sorting via the short syntax: ?sort=-title, the minus means descending |
order |
object | — | Sorting: ?order[title]=asc |
filter |
object | — | Filter by fields from GET /v1/companies/fields.Filtering syntax. Example: ?filter[industry]=IT |
withTotal |
string | — | Whether you need the count: true or false. false — do not request a count. This is the only way to guarantee that meta.total is absent from the response. Without the parameter: the API key setting applies, then the platform default — and in that case a short page still carries the exact count even without an explicit request. Paging and counts |
Examples
curl — personal key
curl "https://vibecode.bitrix24.com/v1/companies?limit=10&filter[industry]=IT&select=id,title,phone" \
-H "X-Api-Key: YOUR_API_KEY"
curl — OAuth application
curl "https://vibecode.bitrix24.com/v1/companies?limit=10&filter[industry]=IT&select=id,title,phone" \
-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/companies?limit=10&filter[industry]=IT', {
headers: {
'X-Api-Key': 'YOUR_API_KEY',
},
})
const { success, data, meta } = await res.json()
console.log(`Found ${meta.total} companies`)
JavaScript — OAuth application
const res = await fetch('https://vibecode.bitrix24.com/v1/companies?limit=10&filter[industry]=IT', {
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 companies (fields — see Fields) |
meta.total |
number | Total number of records. An optional field: if no count was requested, it is absent from the response |
meta.hasMore |
boolean | More records available |
meta.nextAfterId |
string | The identifier of the last returned record. Returned when the sort is strictly id ascending, while hasMore is true. Pass it back as filter[>id] — a cheap replacement for a growing offset |
The card URL of any company from the data array is built from its id:
https://<portal>.bitrix24.com/crm/company/details/<id>/
<portal> is the Bitrix24 portal domain. Access is restricted by the employee's permissions in Bitrix24.
Response example
{
"success": true,
"data": [
{
"id": 1,
"title": "Acme Inc",
"phone": "+15555555555",
"email": "info@example.com",
"assignedById": 1,
"industry": "IT"
}
],
"meta": {
"total": 1430,
"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 |
| 429 | RATE_LIMITED |
Rate limit exceeded: 300 requests per minute per portal, all API keys of the portal share one limit. The exact value arrives in the x-ratelimit-limit header (the cap is divided across replicas). Retry after the delay in the Retry-After header |
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 company 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 company by phone number in any format and by any of its numbers, use Duplicate search.
When to use search. For compound conditions use POST /v1/companies/search. See Search companies.