Close Current Day timeman.close

Scope: timeman

Who can execute the method: any user

The method timeman.close ends the current workday.

Method Parameters

Name `type`	Description
USER_ID `integer`	User identifier. Defaults to the current user
TIME `datetime`	The end time and date of the workday in the ATOM (ISO-8601) format, for example, `2025-02-12T15:52:01+00:00`. The date must match the start date of the workday. 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 `string`	Reason for changing the workday. Required under the conditions: the `TIME` parameter is specified the employee does not have a flexible schedule
LAT `double`	Geographic latitude of the end of the workday
LON `double`	Geographic longitude of the end of the workday

Code Examples

How to Use Examples in Documentation

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

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

try
        {
        	const response = await $b24.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
        		}
        	);
        	
        	const result = response.getData().result;
        	console.info(result);
        }
        catch( error )
        {
        	console.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>';

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 `type`	Description
result `object`	Root element of the response. Contains an object describing the workday
STATUS `string`	Status of the current workday. Possible values: `OPENED` — opened `CLOSED` — closed `PAUSED` — paused `EXPIRED` — expired, meaning opened before the start of the current calendar day and not closed
TIME_START `datetime`	Date and time the workday started. The timezone corresponds to the timezone of the start of the workday
TIME_FINISH `datetime`	Date and time the workday was closed. Returns `null` for an unfinished workday
DURATION `string`	Duration of the workday in `HH:MM:SS` format. Returns `00:00:00` for an unfinished workday
TIME_LEAKS `string`	Total duration of breaks during the day in `HH:MM:SS` format.
ACTIVE `boolean`	Confirmation of the workday. A value of `false` means that the change to the workday is awaiting confirmation from the supervisor
IP_OPEN `string`	IP address from which the workday started
IP_CLOSE `string`	IP address from which the workday was closed. Returns `null` for an unfinished workday
LAT_OPEN `double`	Geographic latitude of the point where the workday started
LON_OPEN `double`	Geographic longitude of the point where the workday started
LAT_CLOSE `double`	Geographic latitude of the point where the workday was closed
LON_CLOSE `double`	Geographic longitude of the point where the workday was closed
TZ_OFFSET `integer`	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 `datetime`	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 `EXPIRED`
time `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 `type`	Description
error `string`	String error code. It may consist of digits, Latin letters, and underscores
error_description `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 `USER_ID` not found
`WRONG_DATETIME`	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: 20x, 40x, 50x

The errors described below may occur when calling any method.

Status	Code Error Message	Description
`500`	`INTERNAL_SERVER_ERROR` Internal server error	An internal server error has occurred, please contact the server administrator or Bitrix24 technical support
`500`	`ERROR_UNEXPECTED_ANSWER` Server returned an unexpected response	An internal server error has occurred, please contact the server administrator or Bitrix24 technical support
`503`	`QUERY_LIMIT_EXCEEDED` Too many requests	The request intensity limit has been exceeded
`405`	`ERROR_BATCH_METHOD_NOT_ALLOWED` Method is not allowed for batch usage	The current method is not allowed to be called using batch
`400`	`ERROR_BATCH_LENGTH_EXCEEDED` Max batch length exceeded	The maximum length of parameters passed to the batch method has been exceeded
`401`	`NO_AUTH_FOUND` Wrong authorization data	Invalid access token or webhook code
`400`	`INVALID_REQUEST` Https required	The methods must be called using the HTTPS protocol
`503`	`OVERLOAD_LIMIT` REST API is blocked due to overload	The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support
`403`	`ACCESS_DENIED` REST API is available only on commercial plans	The REST API is available only on commercial plans
`403`	`INVALID_CREDENTIALS` Invalid request credentials	The user whose access token or webhook was used to call the method lacks permissions
`404`	`ERROR_MANIFEST_IS_NOT_AVAILABLE` Manifest is not available	The manifest is not available
`403`	`insufficient_scope` The request requires higher privileges than provided by the webhook token	The request requires higher privileges than those provided by the webhook token
`401`	`expired_token` The access token provided has expired	The provided access token has expired
`403`	`user_access_error` The user does not have access to the application	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
`500`	`PORTAL_DELETED` Portal was deleted	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

Pause the Current Workday

Get Information About the Current Workday

Close Current Day timeman.close

Method ParametersMethod Parameters

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning