## Postpone an activity

`POST /v1/activities/:id/postpone`

Shifts the start, end and deadline of a CRM activity forward by the given number of seconds. Call it when the activity needs to move to a later time without calculating a new date.

## Parameters

| Parameter | Type | Required | Description |
|----------|-----|:-----:|---------|
| `id` (path) | number | yes | Activity ID, a positive integer. List: [`GET /v1/activities`](/docs/entities/activities/list) |

## Request fields (body)

| Field | Type | Required | Description |
|------|-----|:-----:|---------|
| `offset` | integer | yes | Shift in seconds, an integer greater than zero: `3600` — one hour, `86400` — one day. A number passed as a string, for example `"3600"`, is rejected. To move an activity to an earlier time, see [Change an activity deadline](/docs/entities/activities/deadline) |

The body accepts no other fields.

## Examples

### curl — personal key

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

### curl — OAuth application

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

### JavaScript — personal key

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/activities/3894/postpone', {
  method: 'POST',
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ offset: 3600 }),
})

const { success, data } = await res.json()
console.log('New deadline:', data.deadline)
```

### JavaScript — OAuth application

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

const { success, data } = await res.json()
```

## Response fields

| Field | Type | Description |
|------|-----|---------|
| `success` | boolean | `true` on a successful request |
| `data` | object | The activity, read back after the shift. All fields: [Activity fields](/docs/entities/activities/fields) |
| `data.startTime` | datetime | Activity start after the shift |
| `data.endTime` | datetime | Activity end after the shift |
| `data.deadline` | datetime | Deadline after the shift |

## Response example

An activity with the deadline `2026-10-22T12:00:00.000Z` postponed by one hour. The main fields are shown. Full list: [Activity fields](/docs/entities/activities/fields).

```json
{
  "success": true,
  "data": {
    "id": 3894,
    "ownerTypeId": 3,
    "ownerId": 17,
    "subject": "Call the client",
    "completed": false,
    "status": 1,
    "startTime": "2026-10-22T13:00:00.000Z",
    "endTime": "2026-10-22T13:15:00.000Z",
    "deadline": "2026-10-22T13:00:00.000Z",
    "updatedAt": "2026-10-19T11:47:47.000Z"
  }
}
```

## Error response example

400 — `offset` is not a positive integer:

```json
{
  "success": false,
  "error": {
    "code": "INVALID_PARAMS",
    "message": "offset must be a positive integer in seconds"
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|---------|
| 400 | `INVALID_PARAMS` | `offset` is missing, zero, negative, fractional or passed as a string. Message: `offset must be a positive integer in seconds` |
| 400 | `INVALID_PARAMS` | The body contains a field other than `offset`. Message: `Unsupported action field` |
| 400 | `INVALID_PARAMS` | `id` is not a positive integer. Message: `id must be a positive integer` |
| 404 | `ENTITY_NOT_FOUND` | No activity with this `id` |
| 422 | `ACTIVITY_POSTPONE_NOT_APPLIED` | Bitrix24 confirmed the shift, but the activity start, end and deadline did not change. This check is not performed for a task activity |
| 422 | `BITRIX_ERROR` | Bitrix24 refused to postpone the activity. The refusal text is in `message` |
| 403 | `BITRIX_ACCESS_DENIED` | The key's user has no permission for this activity in Bitrix24 |
| 502 | `BITRIX_ERROR` | The activity has no valid binding to a CRM entity. Message: `Activity has no valid CRM owner` |
| 502 | `BITRIX_ERROR` | The shift was sent, but the activity could not be read back. Message: `Activity could not be read back`. Check the activity state with [`GET /v1/activities/:id`](/docs/entities/activities/get) |
| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is read-only — see [access rights](/docs/access-rights) |
| 403 | `SCOPE_DENIED` | The API key does not have the `crm` scope |
| 401 | `TOKEN_MISSING` | The API key has no configured tokens |

Full list of common API errors: [Errors](/docs/errors).

## Known specifics

**A completed activity is postponed too.** A call on a completed activity returns `200`: the start, end and deadline shift, and `completed` stays `true`.

**For a task activity, the task deadline is shifted.** For an activity with `providerId` equal to `TASKS`, and for an activity with `typeId` equal to `3`, the deadline of the linked task is shifted. The time of the activity itself in `data` may stay the same. Read the new deadline from the task itself: [`GET /v1/tasks/:id`](/docs/entities/tasks/get).

## See also

- [Change an activity deadline](/docs/entities/activities/deadline)
- [Complete an activity](/docs/entities/activities/complete)
- [Get an activity](/docs/entities/activities/get)
- [Activity fields](/docs/entities/activities/fields)