## Pause

`POST /v1/workday/pause`

Pauses the current workday. The status switches to `PAUSED`, and the pause duration accumulates until the day is resumed or closed. The request body may be empty.

## Request fields (body)

| Field | Type | Required | Description |
|------|-----|:-----:|---------|
| `userId` | number | no | Employee identifier. Defaults to the user who owns the key's tokens. Another employee's `userId` is available only to Bitrix24 account administrators and the employee's direct managers. Without those rights Bitrix24 does not return the employee's data |

The body may be empty: `{}`.

## Examples

### curl — personal key

```bash
curl -X POST https://vibecode.bitrix24.com/v1/workday/pause \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'
```

### curl — OAuth application

```bash
curl -X POST https://vibecode.bitrix24.com/v1/workday/pause \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
```

### JavaScript — personal key

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/workday/pause', {
  method: 'POST',
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({}),
})
const { data } = await res.json()
console.log('Status:', data.status)
```

### JavaScript — OAuth application

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/workday/pause', {
  method: 'POST',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({}),
})
const { data } = await res.json()
```

## Response fields

| Field | Type | Description |
|------|-----|---------|
| `success` | boolean | `true` on a successful pause |
| `data` | object | The workday after it was paused |
| `data.status` | string | Status after the pause — `PAUSED` |
| `data.id` | number | Workday record identifier. The same values appear in the [workday history](/docs/workday/records) |
| `data.timeStart` | string | Day start date and time (ISO 8601) |
| `data.timeFinish` | string \| null | Date and time the day finished. `null` until the day is closed, including while it is paused |
| `data.duration` | string | Day duration in `HH:MM:SS` format, excluding pauses. `00:00:00` until the day is closed |
| `data.timeLeaks` | string | Total duration of pauses for the day in `HH:MM:SS` format. The current pause is added to the total once the day is resumed or closed |
| `data.active` | boolean | Whether the workday record is active |
| `data.ipOpen` | string | IP address recorded when the day was started |
| `data.ipClose` | string | IP address recorded when the day was closed. Empty string for a day that has not been closed yet |
| `data.latOpen` | number | Geographic latitude of the start point |
| `data.lonOpen` | number | Geographic longitude of the start point |
| `data.latClose` | number | Geographic latitude of the finish point |
| `data.lonClose` | number | Geographic longitude of the finish point |
| `data.tzOffset` | number | Employee's time zone offset in seconds. Depends on the employee's settings in the Bitrix24 account; the value `7200` corresponds to UTC+2 |

## Response example

```json
{
  "success": true,
  "data": {
    "status": "PAUSED",
    "id": 1,
    "timeStart": "2026-05-05T09:00:00+02:00",
    "timeFinish": null,
    "duration": "00:00:00",
    "timeLeaks": "00:00:00",
    "active": true,
    "ipOpen": "203.0.113.10",
    "ipClose": "",
    "latOpen": 0,
    "lonOpen": 0,
    "latClose": 0,
    "lonClose": 0,
    "tzOffset": 7200
  }
}
```

## Error response example

403 — the key lacks the `timeman` scope:

```json
{
  "success": false,
  "error": {
    "code": "SCOPE_DENIED",
    "message": "This endpoint requires 'timeman' scope"
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|---------|
| 400 | `INVALID_PARAMS` | The `userId` field is not a positive integer, or Bitrix24 rejected a request field as invalid |
| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is missing |
| 401 | `INVALID_API_KEY` | The key is not recognized — no such key exists on the platform |
| 401 | `KEY_EXPIRED` | The API key has expired |
| 401 | `TOKEN_MISSING` | The key has no OAuth tokens configured for the portal |
| 402 | `ACCOUNT_FROZEN` | The portal balance is frozen |
| 403 | `SCOPE_DENIED` | The key lacks the `timeman` scope |
| 409 | `TIMEMAN_MODULE_NOT_ENABLED` | Time Management is not available on this portal: the module is not installed (not included in the plan), or the tool is switched off in portal settings. Ask a portal administrator to enable it — until then every `timeman.*` method answers the same way |
| 422 | `BITRIX_ERROR` | Bitrix24 rejected the request — text is in `message` |
| 429 | `RATE_LIMITED` | The rate limit for requests to Bitrix24 was exceeded |
| 502 | `BITRIX_UNAVAILABLE` | The Bitrix24 portal is unavailable |

The full list of common API errors — [Errors](/docs/errors).

## Known specifics

- **Resuming after a pause is a separate call.** A repeated `/pause` leaves the day in the `PAUSED` status unchanged. To continue the day after a pause, use [`POST /v1/workday/open`](/docs/workday/open) — it switches the day back to `OPENED`.
- **Resuming a closed day.** If the day is already in the `CLOSED` status, the call returns the current state unchanged. To continue a previously closed day, use [`POST /v1/workday/open`](/docs/workday/open).

## See also

- [Open workday](/docs/workday/open)
- [Close workday](/docs/workday/close)
- [Current status](/docs/workday/status)
- [Workday history](/docs/workday/records)
- [Workday](/docs/workday)