For AI agents: markdown of this page — /docs-content-en/entities/items/list.md documentation index — /llms.txt
List smart process items
GET /v1/items/:entityTypeId
Returns a list of items of the specified smart process with filtering, sorting, and pagination.
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
entityTypeId (path) |
number | — | Smart process type ID. List: GET /v1/smart-processes |
limit |
number | 50 |
Number of records (up to 5000) |
offset |
number | 0 |
Skip N records |
order |
object | — | Sorting: ?order[createdTime]=desc |
select |
string | — | Field selection: ?select=id,title,stageId |
filter |
object | — | Filtering by fields from GET /v1/items/:entityTypeId/fields.Filtering syntax. Example: ?filter[assignedById]=1 |
Examples
In the examples entityTypeId = 156 — replace with your smart process ID.
curl — personal key
curl -X GET "https://vibecode.bitrix24.com/v1/items/156?limit=10&order[createdTime]=desc&filter[assignedById]=1" \
-H "X-Api-Key: YOUR_API_KEY"
curl — OAuth application
curl -X GET "https://vibecode.bitrix24.com/v1/items/156?limit=10&order[createdTime]=desc&filter[assignedById]=1" \
-H "X-Api-Key: YOUR_APP_KEY" \
-H "Authorization: Bearer USER_SESSION_TOKEN"
JavaScript — personal key
const params = new URLSearchParams({
limit: '10',
'order[createdTime]': 'desc',
'filter[assignedById]': '1',
})
const res = await fetch(`https://vibecode.bitrix24.com/v1/items/156?${params}`, {
headers: { 'X-Api-Key': 'YOUR_API_KEY' },
})
const { success, data, meta } = await res.json()
console.log(`Found: ${meta.total}`)
JavaScript — OAuth application
const params = new URLSearchParams({
limit: '10',
'order[createdTime]': 'desc',
'filter[assignedById]': '1',
})
const res = await fetch(`https://vibecode.bitrix24.com/v1/items/156?${params}`, {
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
},
})
const { success, data, meta } = await res.json()
Response fields
Pagination is returned in the meta object (as for all list endpoints of the platform), not at the top level.
| Field | Type | Description |
|---|---|---|
data |
array | Array of items |
meta.total |
number | Total number of records |
meta.hasMore |
boolean | Whether more pages exist |
data[].id |
number | Item ID |
data[].title |
string | Name |
data[].stageId |
string | Stage |
data[].categoryId |
number | Pipeline ID |
data[].opportunity |
number | Amount |
data[].currencyId |
string | Currency |
data[].assignedById |
number | Responsible person |
data[].createdTime |
datetime | Creation date |
The card URL of any item from the data array is built from its id:
https://<portal>.bitrix24.com/crm/type/<entityTypeId>/details/<id>/
<entityTypeId> — the smart process type ID (the same as in the request path). <portal> — the Bitrix24 account domain. If the smart process is placed in a separate section of your Bitrix24 account, Bitrix24 opens the card at the corresponding path. Access is restricted by the employee's permissions in Bitrix24.
Response example
{
"success": true,
"data": [
{
"id": 783,
"title": "Supply contract",
"stageId": "DT156_41:NEW",
"categoryId": 41,
"companyId": 15,
"contactId": 42,
"opportunity": 500000,
"currencyId": "USD",
"assignedById": 1,
"createdBy": 1,
"createdTime": "2026-04-15T14:30:00+00:00",
"updatedTime": "2026-04-15T14:30:00+00:00"
}
],
"meta": { "total": 23, "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 |
| 400 | INVALID_DYNAMIC_PARAM |
entityTypeId is not a positive integer or is reserved (1, 2, 3, 4, 7, 31) |
| 400 | UNKNOWN_FILTER_FIELD |
The filter field does not exist on the entity — the message lists the available fields |
Full list of common API errors — Errors.