Pause the current workday timeman.pause
Scope:
timemanWho can execute the method: any user
The method timeman.pause pauses the current workday.
If the workday is completed, the method will resume it and add the time that has passed since completion to the duration.
Method Parameters
|
Name |
Description |
|
USER_ID |
User identifier. By default — the identifier of the current user |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"USER_ID":503}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/timeman.pause
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"USER_ID":503,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/timeman.pause
try
{
const response = await $b24.callMethod(
'timeman.pause',
{
'USER_ID' : 503
}
);
const result = response.getData().result;
console.info(result);
}
catch( error )
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'timeman.pause',
[
'USER_ID' => 503
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
echo 'Info: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error calling timeman.pause: ' . $e->getMessage();
}
BX24.callMethod(
'timeman.pause',
{
'USER_ID' : 503
},
function(result) {
if (result.error()) {
console.error(result.error());
} else {
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'timeman.pause',
[
'USER_ID' => 503
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result": {
"STATUS": "PAUSED",
"TIME_START": "2025-03-27T08:00:01+02:00",
"TIME_FINISH": null,
"DURATION": "00:00:00",
"TIME_LEAKS": "00:00:00",
"ACTIVE": false,
"IP_OPEN": "",
"IP_CLOSE": "",
"LAT_OPEN": 53.548841000000003,
"LON_OPEN": 9.9872739999999993,
"LAT_CLOSE": 0,
"LON_CLOSE": 0,
"TZ_OFFSET": 7200
},
"time": {
"start": 1743057425.9403241,
"finish": 1743057426.0597129,
"duration": 0.11938881874084473,
"processing": 0.08620214462280273,
"date_start": "2025-03-27T09:37:05+03:00",
"date_finish": "2025-03-27T09:37:06+03:00",
"operating_reset_at": 1743058025,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Root element of the response. Contains an object with the description of the workday |
|
STATUS |
Status of the current workday. Possible values:
|
|
TIME_START |
Date and time when the workday started. The timezone corresponds to the timezone of the start of the workday |
|
TIME_FINISH |
Date and time when the workday ended. Returns |
|
DURATION |
Duration of the workday in the format Returns |
|
TIME_LEAKS |
Total duration of breaks during the day in the format |
|
ACTIVE |
Confirmation of the workday. A value of |
|
IP_OPEN |
IP address from which the workday started |
|
IP_CLOSE |
IP address from which the workday ended. Returns |
|
LAT_OPEN |
Geographical latitude of the point where the workday started |
|
LON_OPEN |
Geographical longitude of the point where the workday started |
|
LAT_CLOSE |
Geographical latitude of the point where the workday ended |
|
LON_CLOSE |
Geographical longitude of the point where the workday ended |
|
TZ_OFFSET |
Timezone offset of the employee in which the workday started. The end time of the workday is adjusted to the timezone of the start of the day |
|
TIME_FINISH_DEFAULT |
Recommended value for the end of the day, which can be displayed to the user as a default value. Displayed only for workdays with the status expired |
|
time |
Information about the time taken to process the request |
Error Handling
HTTP status: 400
{
"error":"",
"error_description":"User 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 |
Value |
|
empty string |
User not found |
User with the specified |
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 allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks 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 account administrator has allowed access to this application only for specific users |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Workday: Overview of Methods
- Start a New Workday timeman.open
- Close Current Day timeman.close
- Get information about the current workday timeman.status
- Get User Work Time Settings timeman.settings