Get a List of Custom Field Values for Inventory Accounting Documents catalog.userfield.document.list
Choose a tool for developing with an AI agent:
- use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
- use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation
Scope:
catalogWho can execute the method: a user with the "View Product Catalog" access permission
The method catalog.userfield.document.list returns a paginated list of custom field values for inventory accounting documents.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
select* |
An array containing the list of fields to select (see the fields of the catalog_userfield_document object). Make sure to include |
|
filter* |
An object for filtering the selected records in the format Possible values for You must specify You can add an additional prefix to the key to clarify the filter's behavior. Possible prefix values:
|
|
order |
A sorting object in the format Possible values for Possible values for
If the parameter is not provided, the sorting |
|
start |
This parameter is used to manage pagination. The page size for results is always static — 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":["documentType","documentId","field7097"],"filter":{"documentType":"A","documentId":81},"order":{"documentId":"ASC"},"start":0}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/catalog.userfield.document.list
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"select":["documentType","documentId","field7097"],"filter":{"documentType":"A","documentId":81},"order":{"documentId":"ASC"},"start":0,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/catalog.userfield.document.list
// This snippet is an ES module: top-level await requires type="module" or a bundler.
// $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
import { Text } from '@bitrix24/b24jssdk'
import type { B24Frame } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
// Shape of the payload returned in result (match the "response handling" section of the page)
type UserfieldDocumentListResult = {
documents: Array<{
documentId: number
documentType: string
field7097: string
}>
}
// catalog.userfield.document.list returns a single page (max 50 records). For the whole result set
// use a list helper: $b24.actions.v2.callList.make() returns every record as one
// array, $b24.actions.v2.fetchList.make() yields them in chunks (async generator).
// NOTE: the list helpers do not accept `order` (it is excluded from their params, so
// passing it is a TS error) — keep this call.make + `start` variant when sort matters.
try {
const response = await $b24.actions.v2.call.make<UserfieldDocumentListResult>({
method: 'catalog.userfield.document.list',
params: {
select: ['documentType', 'documentId', 'field7097'],
filter: { documentType: 'A', documentId: 81 },
order: { documentId: 'ASC' },
start: 0,
},
requestId: Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info(result.documents, `page size: ${result.documents.length}`)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function listUserfieldDocuments() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
// catalog.userfield.document.list returns a single page (max 50 records). For the whole result set
// use a list helper: $b24.actions.v2.callList.make() returns every record as one
// array, $b24.actions.v2.fetchList.make() yields them in chunks (async generator).
// NOTE: the list helpers do not accept `order` (it is excluded from their params, so
// passing it is a TS error) — keep this call.make + `start` variant when sort matters.
const response = await $b24.actions.v2.call.make({
method: 'catalog.userfield.document.list',
params: {
select: ['documentType', 'documentId', 'field7097'],
filter: { documentType: 'A', documentId: 81 },
order: { documentId: 'ASC' },
start: 0,
},
requestId: B24Js.Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info(result.documents, `page size: ${result.documents.length}`)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', listUserfieldDocuments)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.catalog.userfield.document.list(
select=[
"documentType",
"documentId",
"field7097",
],
filter={
"documentType": "A",
"documentId": 81,
},
order={
"documentId": "ASC",
},
start=0,
).response
result = bitrix_response.result
print(result)
except BitrixAPIError as error:
print(
"Bitrix API error",
f"error: {error.error}",
f"error_description: {error.error_description}",
sep="\n",
)
except BitrixSDKException as error:
print(f"Bitrix SDK error: {error.message}")
except Exception as error:
print(f"Unexpected error: {error}")
try {
$response = $b24Service
->core
->call(
'catalog.userfield.document.list',
[
'select' => ['documentType', 'documentId', 'field7097'],
'filter' => ['documentType' => 'A', 'documentId' => 81],
'order' => ['documentId' => 'ASC'],
'start' => 0
]
);
print_r($response->getResponseData()->getResult());
} catch (\Throwable $exception) {
echo $exception->getMessage();
}
BX24.callMethod(
'catalog.userfield.document.list',
{
select: ['documentType', 'documentId', 'field7097'],
filter: { documentType: 'A', documentId: 81 },
order: { documentId: 'ASC' }
},
function(result) {
if (result.error()) {
console.error(result.error());
} else {
console.log(result.data());
if (result.more()) {
result.next();
}
}
}
);
require_once('crest.php');
$result = CRest::call(
'catalog.userfield.document.list',
[
'select' => ['documentType', 'documentId', 'field7097'],
'filter' => ['documentType' => 'A', 'documentId' => 81],
'order' => ['documentId' => 'ASC'],
'start' => 0
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "catalog.userfield.document.list", b24.Params{
"select": []string{"documentType", "documentId", "field7097"},
"filter": b24.Params{
"documentType": "A",
"documentId": 81,
},
"order": b24.Params{
"documentId": "ASC",
},
"start": 0,
}, b24.WithIdempotent())
if err != nil {
return fmt.Errorf("catalog.userfield.document.list: %w", err)
}
// The method wraps the response in an object with the "documents" key.
raw, ok := b24.Unwrap(res.Result, "documents")
if !ok {
return fmt.Errorf("no documents key in the response")
}
var items []struct {
DocumentID b24.ID `json:"documentId"`
DocumentType string `json:"documentType"`
Field7097 string `json:"field7097"`
}
if err := json.Unmarshal(raw, &items); err != nil {
return fmt.Errorf("parse response: %w", err)
}
for _, it := range items {
fmt.Println(it.DocumentID)
}
Response Handling
HTTP Code: 200
{
"result": {
"documents": [
{
"documentId": 81,
"documentType": "A",
"field7097": "Test Field"
}
]
},
"total": 1,
"time": {
"start": 1774343822,
"finish": 1774343822.822166,
"duration": 0.8221659660339355,
"processing": 0,
"date_start": "2026-03-24T12:17:02+01:00",
"date_finish": "2026-03-24T12:17:02+01:00",
"operating_reset_at": 1774344422,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
The root element of the response |
|
documents |
A list of objects with values of custom fields for documents. The composition of fields depends on the |
|
next |
Offset for the next page. This field is returned if there are more records |
|
total |
The total number of records. This field is not returned if the request is executed with |
|
time |
Information about the execution time of the request |
Error Handling
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
HTTP Code: 400
{
"error": "0",
"error_description": "The documentType field is not specified in the filter parameter"
}
Possible Error Codes
|
Code |
Description |
Value |
|
|
The documentType field is not specified in the select parameter |
The |
|
|
The documentType field is not specified in the filter parameter |
The |
|
|
Access Denied |
Insufficient rights to read the values of custom fields for documents |
Statuses and System Error Codes
HTTP Status: 4xx, 5xx
The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. A webhook receives a different error message — |
|
|
|
No active webhook with the specified user identifier and secret code was found |
|
|
|
No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope |
|
|
|
The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
The public part of the site is closed. To open it 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 |