Set Time Control Settings timeman.timecontrol.settings.set
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:
timemanWho can execute the method: administrator
The method timeman.timecontrol.settings.set sets the configurations for the time control module.
Data collection for time control begins once the corresponding registration settings are activated. It is not possible to retrieve data for the period prior to activation — the system does not retain historical information retrospectively.
Method Parameters
|
Name |
Description |
|
ACTIVE |
Activate the time control module. Possible values:
|
|
MINIMUM_IDLE_FOR_REPORT |
Minimum idle time in minutes after which a report is required |
|
REGISTER_OFFLINE |
Register offline status |
|
REGISTER_IDLE |
Register idle status |
|
REGISTER_DESKTOP |
Register desktop application status |
|
REPORT_REQUEST_TYPE |
Type of report requests. Possible values:
|
|
REPORT_REQUEST_USERS |
Array of user IDs for whom report requests are required. Filled if |
|
REPORT_SIMPLE_TYPE |
Type of simple report. Possible values:
|
|
REPORT_SIMPLE_USERS |
Array of user IDs with access to the simple report. Filled if |
|
REPORT_FULL_TYPE |
Type of full report. Possible values:
|
|
REPORT_FULL_USERS |
Array of user IDs with access to the full report. Filled if |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ACTIVE":true,"MINIMUM_IDLE_FOR_REPORT":15,"REGISTER_OFFLINE":true,"REGISTER_IDLE":true,"REGISTER_DESKTOP":true,"REPORT_REQUEST_TYPE":"all","REPORT_SIMPLE_TYPE":"all","REPORT_FULL_TYPE":"all"}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/timeman.timecontrol.settings.set
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ACTIVE":true,"MINIMUM_IDLE_FOR_REPORT":15,"REGISTER_OFFLINE":true,"REGISTER_IDLE":true,"REGISTER_DESKTOP":true,"REPORT_REQUEST_TYPE":"all","REPORT_SIMPLE_TYPE":"all","REPORT_FULL_TYPE":"all","auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/timeman.timecontrol.settings.set
try
{
const response = await $b24.callMethod(
'timeman.timecontrol.settings.set',
{
'ACTIVE': true,
'MINIMUM_IDLE_FOR_REPORT': 15,
'REGISTER_OFFLINE': true,
'REGISTER_IDLE': true,
'REGISTER_DESKTOP': true,
'REPORT_REQUEST_TYPE': 'all',
'REPORT_SIMPLE_TYPE': 'all',
'REPORT_FULL_TYPE': 'all'
}
);
const result = response.getData().result;
console.info(result);
}
catch( error )
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'timeman.timecontrol.settings.set',
[
'ACTIVE' => true,
'MINIMUM_IDLE_FOR_REPORT' => 15,
'REGISTER_OFFLINE' => true,
'REGISTER_IDLE' => true,
'REGISTER_DESKTOP' => true,
'REPORT_REQUEST_TYPE' => 'all',
'REPORT_SIMPLE_TYPE' => 'all',
'REPORT_FULL_TYPE' => 'all',
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
// Your logic for processing data
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error setting time control settings: ' . $e->getMessage();
}
BX24.callMethod(
'timeman.timecontrol.settings.set',
{
'ACTIVE': true,
'MINIMUM_IDLE_FOR_REPORT': 15,
'REGISTER_OFFLINE': true,
'REGISTER_IDLE': true,
'REGISTER_DESKTOP': true,
'REPORT_REQUEST_TYPE': 'all',
'REPORT_SIMPLE_TYPE': 'all',
'REPORT_FULL_TYPE': 'all'
},
function(result) {
if (result.error()) {
console.error(result.error());
} else {
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'timeman.timecontrol.settings.set',
[
'ACTIVE' => true,
'MINIMUM_IDLE_FOR_REPORT' => 15,
'REGISTER_OFFLINE' => true,
'REGISTER_IDLE' => true,
'REGISTER_DESKTOP' => true,
'REPORT_REQUEST_TYPE' => 'all',
'REPORT_SIMPLE_TYPE' => 'all',
'REPORT_FULL_TYPE' => 'all'
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": true,
"time": {
"start": 1748526089.625516,
"finish": 1748526089.656787,
"duration": 0.03127098083496094,
"processing": 0.008746147155761719,
"date_start": "2025-05-29T16:41:29+02:00",
"date_finish": "2025-05-29T16:41:29+02:00",
"operating_reset_at": 1748526689,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Execution result. Returns |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error": "ACCESS_ERROR",
"error_description": "You don't have access to use this method"
}
|
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 |
Value |
|
|
You don't have access to use this method |
You do not have access to this method |
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
- Time Tracking: Overview of Methods
- Add Absence Report timeman.timecontrol.report.add
- Get Report on Identified Absences timeman.timecontrol.reports.get
- Get the list of users for the timeman.timecontrol.reports.users.get