Get a List of Warehouse Accounting Documents catalog.document.list
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Scope:
catalogWho can execute the method: a user with the "View product catalog" access permission
The method catalog.document.list returns a paginated list of warehouse accounting documents. By default, filters are applied to the request, limiting the selection to the available document types and the current user's permissions.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
select |
An array of fields from catalog_document that need to be selected. If the array is not provided or an empty array is passed, all available document fields will be selected. |
|
filter |
An object for filtering the selected documents in the format Possible values for An additional prefix can be specified for the key to clarify the filter's behavior. Possible prefix values:
|
|
order |
An object for sorting the selected documents in the format Possible values for Possible values for
By default, documents are sorted in ascending order by |
|
start |
This parameter is used to manage pagination. The page size is 50 records. To select the second page of results, pass the value The formula for calculating the
|
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"select": ["id","docType","docNumber","title","status","dateDocument","total"],
"filter": {">=dateCreate":"2025-10-01T00:00:00+02:00","<=dateCreate":"2025-10-15T23:59:59+02:00"},
"order": {"id":"ASC"},
"start": 50
}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/catalog.document.list
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"select": ["id","docType","docNumber","title","status","dateDocument","total"],
"filter": {">=dateCreate":"2025-10-01T00:00:00+02:00","<=dateCreate":"2025-10-15T23:59:59+02:00"},
"order": {"id":"ASC"},
"start": 50,
"auth": "**put_access_token_here**"
}' \
https://**put_your_bitrix24_address**/rest/catalog.document.list
// callListMethod: Retrieves all data at once.
// Use only for small selections (< 1000 items) due to high
// memory load.
try {
const response = await $b24.callListMethod(
'catalog.document.list',
{
select: ['id', 'docType', 'title', 'status'],
filter: { '>=dateCreate': '2025-10-01T00:00:00+02:00', '<=dateCreate': '2025-10-15T23:59:59+02:00' },
order: { id: 'ASC' }
},
(progress: number) => { console.log('Progress:', progress) }
);
const items = response.getData() || [];
for (const entity of items) { console.log('Entity:', entity) }
} catch (error: any) {
console.error('Request failed', error)
}
// fetchListMethod: Selects data in parts using an iterator.
// Use for large volumes of data for efficient memory consumption.
try {
const generator = $b24.fetchListMethod('catalog.document.list', {
select: ['id', 'docType', 'title', 'status'],
filter: { '>=dateCreate': '2025-10-01T00:00:00+02:00', '<=dateCreate': '2025-10-15T23:59:59+02:00' },
order: { id: 'ASC' },
}, 'ID');
for await (const page of generator) {
for (const entity of page) { console.log('Entity:', entity) }
}
} catch (error: any) {
console.error('Request failed', error)
}
// callMethod: Manual control of pagination through the start parameter.
// Use for precise control over request batches.
// Less efficient for large data than fetchListMethod.
try {
const response = await $b24.callMethod('catalog.document.list', {
select: ['id', 'docType', 'title', 'status'],
filter: { '>=dateCreate': '2025-10-01T00:00:00+02:00', '<=dateCreate': '2025-10-15T23:59:59+02:00' },
order: { id: 'ASC' },
}, 0);
const result = response.getData().result || [];
for (const entity of result) { console.log('Entity:', entity) }
} catch (error: any) {
console.error('Request failed', error)
}
try {
$response = $b24Service
->core
->call(
'catalog.document.list',
[
'select' => ['id', 'docType', 'docNumber', 'title', 'status', 'dateDocument', 'total'],
'filter' => [
'>=dateCreate' => '2025-10-01T00:00:00+02:00',
'<=dateCreate' => '2025-10-15T23:59:59+02:00',
],
'order' => ['ID' => 'ASC'],
'start' => 50, // value of next from the previous response
]
);
$payload = $response
->getResponseData()
->getResult();
print_r($payload['documents']);
$next = $response
->getResponseData()
->getNext();
echo PHP_EOL . 'next: ' . ($next ?? 'null');
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error loading documents: ' . $e->getMessage();
}
BX24.callMethod(
'catalog.document.list',
{
select: ['id', 'docType', 'title', 'status'],
filter: { '>=dateCreate': '2025-10-01T00:00:00+02:00', '<=dateCreate': '2025-10-15T23:59:59+02:00' },
order: { id: 'ASC' }
},
function(result)
{
if (result.error())
{
console.error(result.error());
return;
}
console.table(result.data().documents);
if (result.more())
{
result.next(); // substitutes the value from the response into start and repeats the request
}
}
);
require_once('crest.php');
$result = CRest::call(
'catalog.document.list',
[
'select' => ['id', 'docType', 'docNumber', 'title', 'status', 'dateDocument', 'total'],
'filter' => [
'>=dateCreate' => '2025-10-01T00:00:00+02:00',
'<=dateCreate' => '2025-10-15T23:59:59+02:00',
],
'order' => ['ID' => 'ASC'],
'start' => 50,
]
);
echo '<PRE>';
print_r($result['result']['documents']);
echo PHP_EOL . 'next: ' . ($result['next'] ?? 'null');
echo '</PRE>';
Response Handling
HTTP Code: 200
{
"result": {
"documents": [
{
"docType": "S",
"id": 1,
"status": "Y",
"title": "Receipt #2"
},
{
"docType": "A",
"id": 7,
"status": "N",
"title": "Test Rest"
},
// ...other documents
{
"docType": "S",
"id": 105,
"status": "N",
"title": "receipt 10"
}
]
},
"next": 50,
"total": 143,
"time": {
"start": 1761914886,
"finish": 1761914886.802491,
"duration": 0.8024909496307373,
"processing": 0,
"date_start": "2025-10-31T15:48:06+02:00",
"date_finish": "2025-10-31T15:48:06+02:00",
"operating_reset_at": 1761915486,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
The root element of the response |
|
documents |
A list of documents, the response structure depends on the |
|
next |
Offset pointer for the next page. Pass this value to the |
|
total |
The total number of documents |
|
time |
Information about the request execution time |
Error Handling
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
HTTP Code: 400
{
"error": "0",
"error_description": "Insufficient permissions to save the document"
}
Possible Error Codes
|
Code |
Description |
Value |
|
|
Insufficient permissions to save the document |
The user does not have permission to view |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the portal administrator has restricted access to this application to specific users only |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the "Temporary closure of the public part of the site" option. Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Update Warehouse Accounting Document catalog.document.update
- Get a list of products in inventory documents catalog.document.element.list
- Get a List of Vendor Bindings to Documents catalog.documentcontractor.list