Make a Field Required v 3.0 crm.[type].field.required.set
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:
crmWho can execute the method: a user with the "Edit CRM preferences" permission in CRM
This 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 crm.<type>.field.required.set method makes a field required in the entire pipeline or at selected stages and returns the new configuration. For example, if the "Contract number" field is required at the "Approval" stage, an item cannot be moved to this stage in the card while the field is empty. The object type is set by the <type> segment of the method name.
Method Name for the Object Type
|
Object type |
Method |
Fields |
|
Deal |
|
|
|
Lead |
|
|
|
Contact |
|
|
|
Company |
|
|
|
Estimate |
|
|
|
Invoice |
|
|
|
SPA |
|
For an SPA, the method name includes the type ID entityTypeId. SPA type IDs are returned by the crm.type.list method in the entityTypeId field. SPAs have field requirement methods regardless of the type settings. My company does not have these methods: for crm.mycompany.field.required.set, Bitrix24 returns the "Method Not Found" error.
The method name is written in lowercase: crm.smartinvoice.field.required.set, not crm.smartInvoice.field.required.set. If the name is written in a different case, the method returns the "Method Not Found" error.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
fieldId* |
Field name: a standard field in camelCase, for example, |
|
categoryId |
Pipeline ID. When to pass it |
|
requiredStageIds |
Stages at which the field is required, for example, |
The categoryId Parameter
Bitrix24 stores the field requirement separately for each pipeline. Whether to pass categoryId depends on the object type:
|
Object type |
categoryId |
|
Deal, contact, company |
Required. The default pipeline is set by |
|
SPA |
Required. The pipeline ID is returned by the crm.<type>.category.list method. If pipelines are disabled in the type, the SPA has one pipeline and no pipeline methods. The ID of this pipeline is returned by the crm.category.list method with the |
|
Invoice |
Required. The invoice pipeline ID is returned by the crm.category.list method with |
|
Lead, estimate |
Not passed |
If categoryId does not follow the rules in the table, the method returns an error with the text Invalid category ID.
The requiredStageIds Parameter
The requirement mode depends on this parameter:
- not passed — the field is required at all stages of the pipeline, mode
all. For leads and estimates, in the entire object type - a non-empty array is passed — the field is required only at the specified stages, mode
stages - an empty array
[]is passed — the method removes the requirement, modenone
Pass stages as strings and only from the categoryId pipeline. Deal and SPA stages are returned by the crm.<type>.category.stage.list method. Lead, estimate, and invoice stages are returned by the crm.status.list method. The ENTITY_ID value for it depends on the object type:
- lead —
STATUS - estimate —
QUOTE_STATUS - invoice —
SMART_INVOICE_STAGE_<categoryId>
Contacts and companies have no stages: for them, the method makes the field required in the entire pipeline.
The new configuration replaces the previous one. To add a stage, pass the entire list of stages again.
By default, REST 3.0 item methods do not check a requirement set by this method. For example, if a field is required in the all mode, the crm.<type>.add method still creates an item without this field, and crm.<type>.update moves an item to a stage where the field is required. To make the methods check requirements, enable the "Validate required custom fields in REST" option in the CRM settings.
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}/crm.smartprocess1038.field.required.set
The examples make the "Contract number" field required at the "Approval" stage in pipeline 69 of an SPA with the type ID 1038. For a different object type, replace the method name according to the table above.
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fieldId":"UF_CRM_CONTRACT_NUMBER","categoryId":69,"requiredStageIds":["DT1038_69:CLIENT"]}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/crm.smartprocess1038.field.required.set
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fieldId":"UF_CRM_CONTRACT_NUMBER","categoryId":69,"requiredStageIds":["DT1038_69:CLIENT"],"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/crm.smartprocess1038.field.required.set
CRM methods are not yet included in the list of REST 3.0 methods known to $b24.actions.v3.call.make: such a call returns the SDK error JSSDK_CORE_METHOD_NOT_SUPPORT_IN_API_V3. Call the method through the REST 3.0 HTTP client — $b24.getHttpClient(ApiVersion.v3).call.
import { ApiVersion, Text } from '@bitrix24/b24jssdk'
import type { B24Frame } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
type RequirementResult = {
item: {
fieldId: string
categoryId: number | null
mode: 'none' | 'all' | 'stages'
requiredStageIds: string[]
globallyRequired: boolean
}
}
try {
const response = await $b24.getHttpClient(ApiVersion.v3).call<RequirementResult>(
'crm.smartprocess1038.field.required.set',
{
fieldId: 'UF_CRM_CONTRACT_NUMBER',
categoryId: 69,
requiredStageIds: ['DT1038_69:CLIENT'],
},
Text.getUuidRfc4122()
)
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info(result.item.mode, result.item.requiredStageIds)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
CRM methods are not yet included in the list of REST 3.0 methods known to $b24.actions.v3.call.make. Call the method through the REST 3.0 HTTP client — $b24.getHttpClient(B24Js.ApiVersion.v3).call.
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function setRequirement() {
try {
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.getHttpClient(B24Js.ApiVersion.v3).call(
'crm.smartprocess1038.field.required.set',
{
fieldId: 'UF_CRM_CONTRACT_NUMBER',
categoryId: 69,
requiredStageIds: ['DT1038_69:CLIENT'],
},
B24Js.Text.getUuidRfc4122()
)
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info(result.item.mode, result.item.requiredStageIds)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', setRequirement)
</script>
b24pysdk has no ready-made wrappers for CRM methods, and the SDK sends to REST 3.0 only the methods from the Config().api_v3_methods list. Add the method to this list and call it via bitrix_token.call_method with prefer_version=3.
from b24pysdk import Config
from b24pysdk.errors import BitrixSDKException
from b24pysdk.errors.v3 import BitrixAPIError
method = "crm.smartprocess1038.field.required.set"
Config().configure(api_v3_methods=Config().api_v3_methods | {method})
try:
response = bitrix_token.call_method(
api_method=method,
params={
"fieldId": "UF_CRM_CONTRACT_NUMBER",
"categoryId": 69,
"requiredStageIds": ["DT1038_69:CLIENT"],
},
prefer_version=3,
)
result = response["result"]
print(result["item"]["mode"], result["item"]["requiredStageIds"])
except BitrixAPIError as error:
print(
"Bitrix API error",
f"code: {error.code}",
f"message: {error.error.message}",
sep="\n",
)
except BitrixSDKException as error:
print(f"Bitrix SDK error: {error.message}")
except Exception as error:
print(f"Unexpected error: {error}")
The SDK does not yet support calls to the /rest/api/ address. Use a direct HTTP request, for example, via cURL or fetch.
try {
$response = $b24Service
->core
->call(
'crm.smartprocess1038.field.required.set',
[
'fieldId' => 'UF_CRM_CONTRACT_NUMBER',
'categoryId' => 69,
'requiredStageIds' => ['DT1038_69:CLIENT'],
]
);
$result = $response
->getResponseData()
->getResult();
print_r($result);
} catch (Throwable $e) {
echo $e->getMessage();
}
The SDK does not yet support calls to the /rest/api/ address. Use a direct HTTP request, for example, via cURL or fetch.
BX24.callMethod(
'crm.smartprocess1038.field.required.set',
{
fieldId: 'UF_CRM_CONTRACT_NUMBER',
categoryId: 69,
requiredStageIds: ['DT1038_69:CLIENT'],
},
result => {
if (result.error())
console.error(result.error());
else
console.dir(result.data());
}
);
The SDK does not yet support calls to the /rest/api/ address. Use a direct HTTP request, for example, via cURL or fetch.
require_once('crest.php');
$result = CRest::call(
'crm.smartprocess1038.field.required.set',
[
'fieldId' => 'UF_CRM_CONTRACT_NUMBER',
'categoryId' => 69,
'requiredStageIds' => ['DT1038_69:CLIENT'],
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "crm.smartprocess1038.field.required.set", b24.Params{
"fieldId": "UF_CRM_CONTRACT_NUMBER",
"categoryId": 69,
"requiredStageIds": []string{"DT1038_69:CLIENT"},
})
if err != nil {
return fmt.Errorf("crm.smartprocess1038.field.required.set: %w", err)
}
var out struct {
Item struct {
FieldID string `json:"fieldId"`
Mode string `json:"mode"`
RequiredStageIDs []string `json:"requiredStageIds"`
} `json:"item"`
}
if err := json.Unmarshal(res.Result, &out); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println(out.Item.Mode, out.Item.RequiredStageIDs)
Response Handling
HTTP status: 200
{
"result": {
"item": {
"fieldId": "UF_CRM_CONTRACT_NUMBER",
"categoryId": 69,
"mode": "stages",
"requiredStageIds": [
"DT1038_69:CLIENT"
],
"globallyRequired": false
}
},
"time": {
"start": 1793716020,
"finish": 1793716020.266912,
"duration": 0.26691198348999023,
"processing": 0,
"date_start": "2026-11-03T17:27:00+03:00",
"date_finish": "2026-11-03T17:27:00+03:00",
"operating_reset_at": 1793716620,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Object with response data |
|
result.item |
Field requirement configuration. Configuration fields |
|
time |
Information about the request execution time |
Configuration Fields
|
Name |
Description |
|
fieldId |
Field name |
|
categoryId |
Pipeline ID. For leads and estimates, |
|
mode |
Requirement mode. Possible values:
|
|
requiredStageIds |
Stages at which the field is required. The array is filled in only when |
|
globallyRequired |
Whether the field is required in all pipelines regardless of |
Error Handling
HTTP status: 400
{
"error": {
"code": "BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION",
"message": "Request validation failed.",
"validation": [
{
"message": "A required stage was not found in this context.",
"field": "requiredStageIds"
}
]
}
}
|
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
The "Pipeline Not Found" error is returned with the short code CONTEXT_NOT_FOUND without the BITRIX_REST_V3_ prefix. Its text and the texts of validation errors are in English.
Request Validation Errors
Error Code: BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION
|
Field |
Error description |
How to Fix |
|
|
fieldId must be a non-empty string. |
Pass the field name as a string, for example, |
|
|
Invalid category ID. |
Pass |
|
|
categoryId must be a non-negative integer. |
Pass the pipeline ID as an integer of |
|
|
requiredStageIds must be an array of strings. |
Pass an array of strings. The method does not accept |
|
|
Required stage ID must be a non-empty string. |
Pass stage IDs as strings, for example, |
|
|
A required stage was not found in this context. |
Pass stages of the |
|
|
Stage requirements are not supported in this context. |
Contacts and companies have no stages. Remove |
|
|
Field requirement is not supported for this field. |
Choose a different field: the requirement cannot be configured for |
Field Not Found
Error Code: BITRIX_REST_V3_REALISATION_EXCEPTION_FIELDNOTFOUNDEXCEPTION, HTTP status: 404
|
Field |
Error description |
How to Fix |
|
|
Field |
Check the field name with the crm.<type>.field.list method. Standard field names are written in camelCase: |
Pipeline Not Found
Error Code: CONTEXT_NOT_FOUND, HTTP status: 404
|
Field |
Error description |
How to Fix |
|
|
The field requirement context was not found. |
Check |
Access Denied
Error Code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION, HTTP status: 403
|
Field |
Error description |
How to Fix |
|
|
Access denied |
Call the method on behalf of a user with the "Edit CRM preferences" permission in CRM |
Method Not Found
Error Code: BITRIX_REST_V3_EXCEPTION_METHODNOTFOUNDEXCEPTION, HTTP status: 404
|
Field |
Error description |
How to Fix |
|
|
Method |
Check the method name: it is written in lowercase, for example, |
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 |