Get Recurring Deal Template Settings by ID crm.deal.recurring.get
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: user with "read" access permission for deals
The method crm.deal.recurring.get returns the fields of the recurring deal template settings by its identifier.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Identifier of the recurring deal template settings. The identifier can be obtained using the methods crm.deal.recurring.list or crm.deal.recurring.add |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":15}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/crm.deal.recurring.get
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":15,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/crm.deal.recurring.get
try
{
const response = await $b24.callMethod(
'crm.deal.recurring.get',
{
id: 15,
}
);
const result = response.getData().result;
console.info('Template settings:', result);
}
catch (error)
{
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'crm.deal.recurring.get',
[
'id' => 15,
]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
error_log($result->error());
echo 'Error: ' . $result->error();
} else {
echo 'Recurring settings: ' . print_r($result->data(), true);
}
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error getting recurring settings: ' . $e->getMessage();
}
BX24.callMethod(
'crm.deal.recurring.get',
{
id: 15
},
function(result)
{
if (result.error())
console.error(result.error());
else
console.info(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'crm.deal.recurring.get',
[
'id' => 15
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": {
"ID": "25",
"DEAL_ID": "7591",
"BASED_ID": "7577",
"ACTIVE": "Y",
"CATEGORY_ID": "2",
"IS_LIMIT": "D",
"COUNTER_REPEAT": null,
"LIMIT_REPEAT": null,
"LIMIT_DATE": "2027-03-05T03:00:00+01:00",
"START_DATE": "2026-04-05T03:00:00+01:00",
"NEXT_EXECUTION": "2026-04-05T01:00:00+01:00",
"LAST_EXECUTION": "",
"PARAMS": {
"MODE": "multiple",
"SINGLE_BEFORE_START_DATE_TYPE": null,
"SINGLE_BEFORE_START_DATE_VALUE": 0,
"MULTIPLE_TYPE": "month",
"MULTIPLE_INTERVAL": 1,
"OFFSET_BEGINDATE_TYPE": "day",
"OFFSET_BEGINDATE_VALUE": 1,
"OFFSET_CLOSEDATE_TYPE": "month",
"OFFSET_CLOSEDATE_VALUE": 2
}
},
"time": {
"start": 1772753726,
"finish": 1772753726.940512,
"duration": 0.94051194190979,
"processing": 0,
"date_start": "2026-03-06T02:35:26+01:00",
"date_finish": "2026-03-06T02:35:26+01:00",
"operating_reset_at": 1772754326,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Root element of the response. Contains fields of the recurring deal template settings |
|
time |
Information about the request execution time |
Type recurring_deal
|
Name |
Description |
|
ID |
Identifier of the record in the recurring deal settings table |
|
DEAL_ID |
Identifier of the deal for which the recurrence is set |
|
BASED_ID |
Identifier of the deal on which the template is based |
|
ACTIVE |
Active flag. Possible values:
|
|
NEXT_EXECUTION |
Date and time of the next deal creation from the template |
|
LAST_EXECUTION |
Date and time of the last deal creation from the template. May be an empty string if there have been no executions yet |
|
COUNTER_REPEAT |
Number of deals created from the template. |
|
START_DATE |
Date to start calculating the next execution. Returned in the format |
|
CATEGORY_ID |
Identifier of the funnel for created deals |
|
IS_LIMIT |
Type of limitation on deal creation:
|
|
LIMIT_REPEAT |
Maximum number of deals to be created. Used when |
|
LIMIT_DATE |
End date for deal generation. Used when Returned in the format |
|
PARAMS |
Recurrence parameters (detailed description) |
Fields of the PARAMS Object
|
Name |
Description |
|
MODE |
Recurrence mode:
|
|
MULTIPLE_TYPE |
Period type for
|
|
MULTIPLE_INTERVAL |
Recurrence interval for |
|
SINGLE_BEFORE_START_DATE_TYPE |
Offset type for
|
|
SINGLE_BEFORE_START_DATE_VALUE |
Offset value for For |
|
OFFSET_BEGINDATE_TYPE |
Type of offset for the start date of the created deal:
|
|
OFFSET_BEGINDATE_VALUE |
Offset value for the start date of the created deal |
|
OFFSET_CLOSEDATE_TYPE |
Type of offset for the end date of the created deal:
|
|
OFFSET_CLOSEDATE_VALUE |
Offset value for the end date of the created deal |
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 |
|
|
Recurring deals are not available in Bitrix24 |
|
|
The recurring deal template was not found |
|
|
Insufficient rights to read the recurring deal 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
- Get the List of Fields for the Recurring Deal Template crm.deal.recurring.fields
- Get a List of Recurring Deal Template Settings crm.deal.recurring.list
- Create a Template for Recurring Deal crm.deal.recurring.add
- Update the Recurring Deal Template Settings `crm.deal.recurring.update`
- Delete the Recurring Deal Template Setting crm.deal.recurring.delete
- Create a New Deal from the Template crm.deal.recurring.expose