Close Current Day timeman.close
Choose a tool for developing with an AI agent:
- use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
- use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation
Scope:
timemanWho can execute the method: any user
The method timeman.close ends the current workday.
Method Parameters
|
Name |
Description |
|
USER_ID |
User identifier. Defaults to the current user |
|
TIME |
The end time and date of the workday in the ATOM (ISO-8601) format, for example, By default, the workday is closed at the current moment in the timezone where the workday was started. If the end timezone differs from the start timezone, the end time is automatically converted to the timezone in which the day was started. |
|
REPORT |
Reason for changing the workday. Required under the conditions:
|
|
LAT |
Geographic latitude of the end of the workday |
|
LON |
Geographic longitude of the end of the workday |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"USER_ID":503,"TIME":"2025-03-27T17:00:01+00:00","REPORT":"Forgot to close the workday","LAT":53.548841,"LON":9.987274}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/timeman.close
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"USER_ID":503,"TIME":"2025-03-27T17:00:01+00:00","REPORT":"Forgot to close the workday","LAT":53.548841,"LON":9.987274,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/timeman.close
// This snippet is an ES module: top-level await requires type="module" or a bundler.
// $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
import { Text } from '@bitrix24/b24jssdk'
import type { B24Frame, ISODate } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
// Shape of the payload returned in result (match the "response handling" section of the page)
type TimemanCloseResult = {
STATUS: string,
TIME_START: ISODate,
TIME_FINISH: ISODate | null,
DURATION: string,
TIME_LEAKS: string,
ACTIVE: boolean,
IP_OPEN: string,
IP_CLOSE: string | null,
LAT_OPEN: number,
LON_OPEN: number,
LAT_CLOSE: number,
LON_CLOSE: number,
TZ_OFFSET: number,
TIME_FINISH_DEFAULT?: ISODate | null,
}
try {
const response = await $b24.actions.v2.call.make<TimemanCloseResult>({
method: 'timeman.close',
params: {
USER_ID: 503,
TIME: '2025-03-27T17:00:01+00:00',
REPORT: 'Forgot to close the workday',
LAT: 53.548841,
LON: 9.987274,
},
requestId: Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info(result.STATUS, result.TIME_START, result.TIME_FINISH, result.DURATION)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function closeWorkday() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'timeman.close',
params: {
USER_ID: 503,
TIME: '2025-03-27T17:00:01+00:00',
REPORT: 'Forgot to close the workday',
LAT: 53.548841,
LON: 9.987274,
},
requestId: B24Js.Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info(result.STATUS, result.TIME_START, result.TIME_FINISH, result.DURATION)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', closeWorkday)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.timeman.close(
user_id=503,
time="2025-03-27T17:00:01+00:00",
report="Forgot to close the workday",
lat=53.548841,
lon=9.987274,
).response
result = bitrix_response.result
print(result)
except BitrixAPIError as error:
print(
"Bitrix API error",
f"error: {error.error}",
f"error_description: {error.error_description}",
sep="\n",
)
except BitrixSDKException as error:
print(f"Bitrix SDK error: {error.message}")
except Exception as error:
print(f"Unexpected error: {error}")
try {
$response = $b24Service
->core
->call(
'timeman.close',
[
'USER_ID' => 503,
'TIME' => '2025-03-27T17:00:01+00:00',
'REPORT' => 'Forgot to close the workday',
'LAT' => 53.548841,
'LON' => 9.987274,
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
// Your data processing logic
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error closing timeman: ' . $e->getMessage();
}
BX24.callMethod(
'timeman.close',
{
'USER_ID' : 503,
'TIME': '2025-03-27T17:00:01+00:00',
'REPORT': 'Forgot to close the workday',
'LAT': 53.548841,
'LON': 9.987274
},
function(result) {
if (result.error()) {
console.error(result.error());
} else {
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'timeman.close',
[
'USER_ID' => 503,
'TIME' => '2025-03-27T17:00:01+00:00',
'REPORT' => 'Forgot to close the workday',
'LAT' => 53.548841,
'LON' => 9.987274
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "timeman.close", b24.Params{
"USER_ID": 503,
"TIME": "2025-03-27T17:00:01+00:00",
"REPORT": "Forgot to close the workday",
"LAT": 53.548841,
"LON": 9.987274,
})
if err != nil {
return fmt.Errorf("timeman.close: %w", err)
}
var item struct {
Status string `json:"STATUS"`
TimeStart string `json:"TIME_START"`
TimeFinish string `json:"TIME_FINISH"`
Duration string `json:"DURATION"`
TimeLeaks string `json:"TIME_LEAKS"`
Active bool `json:"ACTIVE"`
}
if err := json.Unmarshal(res.Result, &item); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println(item.Status, item.TimeStart)
Response Handling
HTTP Status: 200
{
"result": {
"STATUS": "CLOSED",
"TIME_START": "2025-03-27T08:00:01+02:00",
"TIME_FINISH": "2025-03-27T19:00:01+02:00",
"DURATION": "09:37:04",
"TIME_LEAKS": "01:22:56",
"ACTIVE": false,
"IP_OPEN": "",
"IP_CLOSE": "83.219.151.30",
"LAT_OPEN": 53.548841000000003,
"LON_OPEN": 9.9872739999999993,
"LAT_CLOSE": 53.548841000000003,
"LON_CLOSE": 9.9872739999999993,
"TZ_OFFSET": 7200
},
"time": {
"start": 1743057653.725821,
"finish": 1743057654.0894129,
"duration": 0.36359190940856934,
"processing": 0.3278491497039795,
"date_start": "2025-03-27T09:40:53+03:00",
"date_finish": "2025-03-27T09:40:54+03:00",
"operating_reset_at": 1743058253,
"operating": 0.32782983779907227
}
}
Returned Data
|
Name |
Description |
|
result |
Root element of the response. Contains an object describing the workday |
|
STATUS |
Status of the current workday. Possible values:
|
|
TIME_START |
Date and time the workday started. The timezone corresponds to the timezone of the start of the workday |
|
TIME_FINISH |
Date and time the workday was closed. Returns |
|
DURATION |
Duration of the workday in Returns |
|
TIME_LEAKS |
Total duration of breaks during the day in |
|
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 was closed. Returns |
|
LAT_OPEN |
Geographic latitude of the point where the workday started |
|
LON_OPEN |
Geographic longitude of the point where the workday started |
|
LAT_CLOSE |
Geographic latitude of the point where the workday was closed |
|
LON_CLOSE |
Geographic longitude of the point where the workday was closed |
|
TZ_OFFSET |
Timezone offset of the employee in which the workday was 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 presented to the user as a default value. Displayed only for workdays in the expired status |
|
time |
Information about the time taken to process the request |
Error Handling
HTTP Status: 400
{
"error":"WRONG_DATETIME",
"error_description":"Day close date should correspond to the day open date"
}
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
Possible Error Codes
|
Code |
Description |
Value |
|
empty string |
User not found |
User with the specified |
|
|
Day close date should correspond to the day open date |
The closing date of the workday must match the opening date |
Statuses and System Error Codes
HTTP Status: 4xx, 5xx
The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. A webhook receives a different error message — |
|
|
|
No active webhook with the specified user identifier and secret code was found |
|
|
|
No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope |
|
|
|
The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
The public part of the site is closed. To open it 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 |