Get List of Service Fields v 3.0 catalog.product.service.field.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: any user
The method belongs to REST 3.0. The call specifics and response format of the new API version are described in the REST 3.0 overview.
The catalog.product.service.field.list method returns the list of available service fields.
Method Parameters
|
Name |
Description |
|
select |
An array of strings with the names of the description properties to return in the response. Available fields:
Default: all description properties |
Code Examples
How to Use Examples in Documentation
The new API call differs by adding the /api/ segment to the request URL:
https://{installation_address}/rest/api/{user_id}/{webhook_token}/catalog.product.service.field.list
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"select":["name","type","requiredGroups","editableGroups"]}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/catalog.product.service.field.list
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"select":["name","type","requiredGroups","editableGroups"],"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/catalog.product.service.field.list
import { Text } from '@bitrix24/b24jssdk'
import type { B24Frame } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
type ServiceFieldListResult = {
items: Array<{
name?: string
type?: string
requiredGroups?: string[] | null
editableGroups?: string[] | null
}>
}
try {
const response = await $b24.actions.v3.call.make<ServiceFieldListResult>({
method: 'catalog.product.service.field.list',
params: {
select: ['name', 'type', 'requiredGroups', 'editableGroups'],
},
requestId: Text.getUuidRfc4122()
})
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info('Fields:', result.items.length)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function listServiceFields() {
try {
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v3.call.make({
method: 'catalog.product.service.field.list',
params: {
select: ['name', 'type', 'requiredGroups', 'editableGroups'],
},
requestId: B24Js.Text.getUuidRfc4122()
})
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info('Fields:', result.items.length)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', listServiceFields)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.catalog.product.service.field.list(
select=["name", "type", "requiredGroups", "editableGroups"],
).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}")
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via cURL or fetch.
try {
$response = $b24Service
->core
->call(
'catalog.product.service.field.list',
[
'select' => ['name', 'type', 'requiredGroups', 'editableGroups'],
]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
error_log($result->error());
} else {
echo 'Success: ' . print_r($result->data(), true);
}
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error: ' . $e->getMessage();
}
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via cURL or fetch.
BX24.callMethod(
'catalog.product.service.field.list',
{
select: ['name', 'type', 'requiredGroups', 'editableGroups'],
},
result => {
if (result.error())
console.error(result.error());
else
console.dir(result.data());
}
);
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via cURL or fetch.
require_once('crest.php');
$result = CRest::call(
'catalog.product.service.field.list',
[
'select' => ['name', 'type', 'requiredGroups', 'editableGroups'],
]
);
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.product.service.field.list", b24.Params{
"select": []string{"name", "type", "requiredGroups", "editableGroups"},
}, b24.WithIdempotent())
if err != nil {
return fmt.Errorf("catalog.product.service.field.list: %w", err)
}
var result struct {
Items []struct {
Name string `json:"name"`
Type string `json:"type"`
} `json:"items"`
}
if err := json.Unmarshal(res.Result, &result); err != nil {
return fmt.Errorf("parse response: %w", err)
}
for _, field := range result.Items {
fmt.Println(field.Name, field.Type)
}
Response Handling
HTTP status: 200
The method returns descriptions of 48 fields. The example shows the first four.
{
"result": {
"items": [
{
"name": "id",
"type": "int",
"requiredGroups": null,
"editableGroups": null
},
{
"name": "iblockId",
"type": "int",
"requiredGroups": [
"add"
],
"editableGroups": [
"add"
]
},
{
"name": "name",
"type": "string",
"requiredGroups": [
"add"
],
"editableGroups": [
"add",
"update"
]
},
{
"name": "code",
"type": "string",
"requiredGroups": null,
"editableGroups": [
"add",
"update"
]
}
]
},
"time": {
"start": 1792660853,
"finish": 1792660853.574755,
"duration": 0.5747549533843994,
"processing": 0,
"date_start": "2026-10-22T12:20:53+02:00",
"date_finish": "2026-10-22T12:20:53+02:00",
"operating_reset_at": 1792661400,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
An object with the response data |
|
result.items |
An array of field descriptions: |
|
time |
Information about the request execution time |
Items Element
|
Name |
Description |
|
name |
Field name |
|
type |
Type in the metadata: |
|
title |
Field title. Matches |
|
description |
Field description. |
|
validationRules |
Validation rules. An empty array for service fields |
|
requiredGroups |
Operations in which the field is required. |
|
filterable |
|
|
sortable |
|
|
editable |
|
|
editableGroups |
Operations in which the field can be set: |
|
multiple |
Multiple value flag in the metadata. |
|
elementType |
Element type of a composite field. |
Error Handling
HTTP status: 400
{
"error": {
"code": "BITRIX_REST_V3_EXCEPTION_UNKNOWNDTOPROPERTYEXCEPTION",
"message": "Unknown field \"foo\" found in entity \"DtoFieldDto\"."
}
}
|
Name |
Description |
|
error.code |
String error code. Use it to identify the type of exception |
|
error.message |
Text description of the error |
|
error.validation |
Array with error details. Present only in data validation errors |
|
error.validation[].field |
Name of the field where the validation error occurred |
|
error.validation[].message |
Description of the error related to the specified field |
Possible Error Codes
Errors in the select Parameter
Error Code: BITRIX_REST_V3_EXCEPTION_UNKNOWNDTOPROPERTYEXCEPTION
|
Field |
Error description |
How to Fix |
|
|
Unknown field |
Pass only the properties from the |
select Format Errors
Error Code: BITRIX_REST_V3_EXCEPTION_INVALIDSELECTEXCEPTION
|
Field |
Error description |
How to Fix |
|
|
Invalid field in |
Pass |
Access Error
Error Code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION
HTTP status: 403
|
Field |
Error description |
How to Fix |
|
|
Access denied |
Check the user's permissions and the |
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 |