Update the Recurring Deal Template Settings crm.deal.recurring.update
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: a user with "read" and "modify" access permissions for deals
The method crm.deal.recurring.update updates an existing recurring deal template setting.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
The identifier of the recurring deal template setting. The identifier can be obtained using the methods crm.deal.recurring.list or crm.deal.recurring.add |
|
fields |
An object in the following format:
where:
The list of available fields is described below |
Fields Parameter
|
Name |
Description |
|
ACTIVE |
The active flag for the setting. Possible values:
|
|
CATEGORY_ID |
The ID of the funnel for new deals created from the template. The list of available funnels can be obtained using the method crm.category.list by passing |
|
IS_LIMIT |
Limit on creating new deals:
|
|
LIMIT_REPEAT |
The maximum number of deals that can be created from the template. Used when |
|
LIMIT_DATE |
The end date for generating deals from the template in the format |
|
START_DATE |
The start date for calculating the next run in the format |
|
PARAMS |
Recurrence parameters (detailed description) |
PARAMS Parameter
|
Name |
Description |
|
MODE |
The recurrence mode:
|
|
MULTIPLE_TYPE |
The period type for
|
|
MULTIPLE_INTERVAL |
The recurrence interval for |
|
SINGLE_BEFORE_START_DATE_TYPE |
The offset type for
|
|
SINGLE_BEFORE_START_DATE_VALUE |
The offset value for |
|
OFFSET_BEGINDATE_TYPE |
The offset type for the start date of the created deal:
|
|
OFFSET_BEGINDATE_VALUE |
The offset value for the start date of the created deal |
|
OFFSET_CLOSEDATE_TYPE |
The offset type for the completion date of the created deal:
|
|
OFFSET_CLOSEDATE_VALUE |
The offset value for the completion date of the created deal |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":15,"fields":{"ACTIVE":"Y","CATEGORY_ID":"2","IS_LIMIT":"D","LIMIT_DATE":"2027-03-05","START_DATE":"2026-04-05","PARAMS":{"MODE":"multiple","MULTIPLE_TYPE":"month","MULTIPLE_INTERVAL":1,"OFFSET_BEGINDATE_TYPE":"day","OFFSET_BEGINDATE_VALUE":1,"OFFSET_CLOSEDATE_TYPE":"month","OFFSET_CLOSEDATE_VALUE":2}}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/crm.deal.recurring.update
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":15,"fields":{"ACTIVE":"Y","CATEGORY_ID":"2","IS_LIMIT":"D","LIMIT_DATE":"2027-03-05","START_DATE":"2026-04-05","PARAMS":{"MODE":"multiple","MULTIPLE_TYPE":"month","MULTIPLE_INTERVAL":1,"OFFSET_BEGINDATE_TYPE":"day","OFFSET_BEGINDATE_VALUE":1,"OFFSET_CLOSEDATE_TYPE":"month","OFFSET_CLOSEDATE_VALUE":2}},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/crm.deal.recurring.update
try
{
const response = await $b24.callMethod(
'crm.deal.recurring.update',
{
id: 15,
fields: {
ACTIVE: 'Y',
CATEGORY_ID: '2',
IS_LIMIT: 'D',
LIMIT_DATE: '2027-03-05',
START_DATE: '2026-04-05',
PARAMS: {
MODE: 'multiple',
MULTIPLE_TYPE: 'month',
MULTIPLE_INTERVAL: 1,
OFFSET_BEGINDATE_TYPE: 'day',
OFFSET_BEGINDATE_VALUE: 1,
OFFSET_CLOSEDATE_TYPE: 'month',
OFFSET_CLOSEDATE_VALUE: 2,
}
}
}
);
const result = response.getData().result;
console.info('Template updated:', result);
}
catch (error)
{
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'crm.deal.recurring.update',
[
'id' => 15,
'fields' => [
'ACTIVE' => 'Y',
'CATEGORY_ID' => '2',
'IS_LIMIT' => 'D',
'LIMIT_DATE' => '2027-03-05',
'START_DATE' => '2026-04-05',
'PARAMS' => [
'MODE' => 'multiple',
'MULTIPLE_TYPE' => 'month',
'MULTIPLE_INTERVAL' => 1,
'OFFSET_BEGINDATE_TYPE' => 'day',
'OFFSET_BEGINDATE_VALUE' => 1,
'OFFSET_CLOSEDATE_TYPE' => 'month',
'OFFSET_CLOSEDATE_VALUE' => 2,
],
],
]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
error_log($result->error());
echo 'Error: ' . $result->error();
} else {
echo 'Success: ' . var_export($result->data(), true);
}
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error updating recurring deal settings: ' . $e->getMessage();
}
BX24.callMethod(
'crm.deal.recurring.update',
{
id: 15,
fields: {
ACTIVE: 'Y',
CATEGORY_ID: '2',
IS_LIMIT: 'D',
LIMIT_DATE: '2027-03-05',
START_DATE: '2026-04-05',
PARAMS: {
MODE: 'multiple',
MULTIPLE_TYPE: 'month',
MULTIPLE_INTERVAL: 1,
OFFSET_BEGINDATE_TYPE: 'day',
OFFSET_BEGINDATE_VALUE: 1,
OFFSET_CLOSEDATE_TYPE: 'month',
OFFSET_CLOSEDATE_VALUE: 2
}
}
},
function(result)
{
if (result.error())
console.error(result.error());
else
console.info('Template updated:', result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'crm.deal.recurring.update',
[
'id' => 15,
'fields' => [
'ACTIVE' => 'Y',
'CATEGORY_ID' => '2',
'IS_LIMIT' => 'D',
'LIMIT_DATE' => '2027-03-05',
'START_DATE' => '2026-04-05',
'PARAMS' => [
'MODE' => 'multiple',
'MULTIPLE_TYPE' => 'month',
'MULTIPLE_INTERVAL' => 1,
'OFFSET_BEGINDATE_TYPE' => 'day',
'OFFSET_BEGINDATE_VALUE' => 1,
'OFFSET_CLOSEDATE_TYPE' => 'month',
'OFFSET_CLOSEDATE_VALUE' => 2
]
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": true,
"time": {
"start": 1772731825,
"finish": 1772731825.579511,
"duration": 0.5795109272003174,
"processing": 0,
"date_start": "2026-03-05T20:30:25+02:00",
"date_finish": "2026-03-05T20:30:25+02:00",
"operating_reset_at": 1772732425,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
The root element of the response. Returns |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error": "",
"error_description": "Recurring deal is not found."
}
|
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 parameter |
|
|
The parameter |
|
|
Recurring deals are not available in Bitrix24 |
|
|
The recurring deal template was not found |
|
|
Insufficient permissions to read or modify the associated deal |
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
- Get the List of Fields for the Recurring Deal Template crm.deal.recurring.fields
- Get Recurring Deal Template Settings by ID crm.deal.recurring.get
- Get a List of Recurring Deal Template Settings crm.deal.recurring.list
- Create a Template for Recurring Deal crm.deal.recurring.add
- Delete the Recurring Deal Template Setting crm.deal.recurring.delete
- Create a New Deal from the Template crm.deal.recurring.expose