Create a Template crm.requisite.preset.add
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:
crmWho can execute the method: any user
This method creates a new requisites template.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
fields* |
A set of fields — an object of the form |
Parameter fields
Required parameters are marked with *
|
Name |
Description |
|
ENTITY_TYPE_ID* |
Identifier of the parent object's type. Currently, this is only "Requisite" (identifier The identifiers of CRM object types are provided by the method crm.enum.ownertype |
|
COUNTRY_ID* |
Identifier of the country corresponding to the set of fields in the requisites template (for available values, see the method crm.requisite.preset.countries) |
|
NAME* |
Name of the requisite |
|
XML_ID |
External key. Used for exchange operations. Identifier of the external information base object. The purpose of the field may change by the final developer. Each application ensures the uniqueness of values in this field. It is recommended to use a unique prefix to avoid collisions with other applications. Values of the form |
|
ACTIVE |
Activity status. Values |
|
SORT |
Sorting |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"ENTITY_TYPE_ID":8,"COUNTRY_ID":1,"NAME":"IP","XML_ID":"EXAMPLE_COMPANY__VALUE_1","ACTIVE":"Y","SORT":520}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/crm.requisite.preset.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"ENTITY_TYPE_ID":8,"COUNTRY_ID":1,"NAME":"IP","XML_ID":"EXAMPLE_COMPANY__VALUE_1","ACTIVE":"Y","SORT":520},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/crm.requisite.preset.add
try
{
const response = await $b24.callMethod(
"crm.requisite.preset.add",
{
fields:
{
"ENTITY_TYPE_ID": 8, // For the requisites template, "Requisite" (identifier 8) is always specified, see crm.enum.ownertype
"COUNTRY_ID": 1, // USA
"NAME": "IP",
"XML_ID": "EXAMPLE_COMPANY__VALUE_1", // Unique external identifier
"ACTIVE": "Y",
"SORT": 520 // Order in the list of templates
}
}
);
const result = response.getData().result;
console.info("Template created with ID " + result);
}
catch( error )
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'crm.requisite.preset.add',
[
'fields' => [
'ENTITY_TYPE_ID' => 8,
'COUNTRY_ID' => 1,
'NAME' => 'IP',
'XML_ID' => 'EXAMPLE_COMPANY__VALUE_1',
'ACTIVE' => 'Y',
'SORT' => 520,
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Template created with ID ' . $result;
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error creating template: ' . $e->getMessage();
}
BX24.callMethod(
"crm.requisite.preset.add",
{
fields:
{
"ENTITY_TYPE_ID": 8, // For the requisites template, "Requisite" (identifier 8) is always specified, see crm.enum.ownertype
"COUNTRY_ID": 1, // USA
"NAME": "IP",
"XML_ID": "EXAMPLE_COMPANY__VALUE_1", // Unique external identifier
"ACTIVE": "Y",
"SORT": 520 // Order in the list of templates
}
},
function(result)
{
if(result.error())
console.error(result.error());
else
console.info("Template created with ID " + result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'crm.requisite.preset.add',
[
'fields' =>
[
'ENTITY_TYPE_ID' => 8,
'COUNTRY_ID' => 1,
'NAME' => 'IP',
'XML_ID' => 'EXAMPLE_COMPANY__VALUE_1',
'ACTIVE' => 'Y',
'SORT' => 520
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result": 347,
"time": {
"start": 1716543593.35189,
"finish": 1716543593.683898,
"duration": 0.33200788497924805,
"processing": 0.016175031661987305,
"date_start": "2024-05-24T11:39:53+02:00",
"date_finish": "2024-05-24T11:39:53+02:00",
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Identifier of the created requisites template |
|
time |
Information about the request execution time |
Error Handling
HTTP status: 40x, 50x
{
"error": "",
"error_description": "ENTITY_TYPE_ID is not defined or invalid"
}
|
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 |
Possible Error Codes
|
Code |
Description |
|
|
The identifier of the parent object's type is not defined or has an invalid value |
|
|
Insufficient access permissions to add the template |
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 Requisite Template crm.requisite.preset.update
- Get a list of countries for the template crm.requisite.preset.countries
- Get Requisite Template Fields by ID crm.requisite.preset.get
- Get a list of requisites templates by filter crm.requisite.preset.list
- Delete the CRM Requisite Template `crm.requisite.preset.delete`
- Get Description of the Fields of the Requisite Template crm.requisite.preset.fields