## Get event

`GET /v1/calendar-events/:id`

Returns a single calendar event by ID.

## Parameters

| Parameter | Type | Required | Description |
|----------|-----|:-----:|---------|
| `id` (path) | number | yes | Event ID |
| `include` (query) | string | no | Related employees: `owner`, `host`, `attendee`. See the "Related data" section below |
| `select` (query) | string | no | Comma-separated response fields, for example `name,from`. Without the parameter, all fields are returned. The `id` field is always returned. Names come from [Event fields](./fields.md) |

## Examples

### curl — personal key

```bash
curl "https://vibecode.bitrix24.com/v1/calendar-events/7773" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### curl — OAuth application

```bash
curl "https://vibecode.bitrix24.com/v1/calendar-events/7773" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"
```

### JavaScript — personal key

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/calendar-events/7773', {
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
  },
})

const { success, data } = await res.json()
console.log(data.name, '—', data.from)
```

### JavaScript — OAuth application

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/calendar-events/7773', {
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

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

## Response fields

| Field | Type | Description |
|------|-----|---------|
| `success` | boolean | Always `true` on success |
| `data` | object | The event (all fields — see [Event fields](./fields.md)) |
| `meta.warnings` | array | Returned when a name that is absent from the event schema is listed alongside `*` in `select`: the event comes back without that field. Each warning is an object with `code`, `field` and `message`, and the code is `UNKNOWN_SELECT_FIELD`. Without `*`, such a name causes the whole request to be rejected |

## Related data

To get the employees related to the event along with the event itself, pass the `include` parameter in the GET request:

```
GET /v1/calendar-events/7773?include=owner,host,attendee
```

Available `include` values — up to three names per request:

| Name | Source field | Key in `_included` | Result |
|------|--------------|--------------------|--------|
| `owner` | `ownerId` — the calendar owner | `owner` | Employee card or `null` |
| `host` | `meetingHost` — the meeting organizer | `host` | Employee card or `null`. For `type: group`, a card is returned only when `isMeeting: true`; otherwise `_included.host` is `null`. For a non-meeting event in that calendar, `meetingHost` holds the workgroup ID. The event creator is identified by `createdBy` |
| `attendee` | `attendeeList` — the invitees | `users` | Array of cards in `attendeeList` order. An empty array if there are no invitees |

The employee card is the same as in the [`GET /v1/users/:id`](/docs/entities/users/get) response. Retrieving a related employee requires the key to have the `user` scope in addition to `calendar`. The result is in the `_included` field:

```json
{
  "success": true,
  "data": {
    "id": 7773,
    "name": "Team call",
    "ownerId": 1,
    "meetingHost": 1,
    "attendeeList": [
      { "id": 1, "entryId": "7773", "status": "H" }
    ],
    "_included": {
      "owner": { "id": 1, "name": "John", "lastName": "Brown", "email": "john.brown@example.com", "active": true },
      "host": { "id": 1, "name": "John", "lastName": "Brown", "email": "john.brown@example.com", "active": true },
      "users": [
        { "id": 1, "name": "John", "lastName": "Brown", "email": "john.brown@example.com", "active": true }
      ]
    }
  }
}
```

Only the main event and employee fields are shown. For the full card, see [Employee fields](/docs/entities/users/fields).

## Response example

```json
{
  "success": true,
  "data": {
    "id": 7773,
    "parentId": 7773,
    "deleted": false,
    "type": "user",
    "ownerId": 1,
    "name": "Team call",
    "from": "2026-06-10T10:00:00+00:00",
    "to": "2026-06-10T11:00:00+00:00",
    "skipTime": false,
    "durationSeconds": 3600,
    "createdBy": 1,
    "dateCreate": "06/05/2026 09:12:00 am",
    "updatedAt": "06/05/2026 09:12:00 am",
    "description": "Weekly sync",
    "accessibility": "busy",
    "importance": "normal",
    "isMeeting": false,
    "meetingStatus": "H",
    "meetingHost": 1,
    "sectionId": 3,
    "attendeeList": [
      { "id": 1, "entryId": "7773", "status": "H" }
    ],
    "crmFields": ["D_741", "C_9"]
  }
}
```

## Error response example

404 — event not found:

```json
{
  "success": false,
  "error": {
    "code": "ENTITY_NOT_FOUND",
    "message": "calendarEvent 99999999 not found"
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|---------|
| 404 | `ENTITY_NOT_FOUND` | The event with the specified `id` does not exist |
| 400 | `INVALID_INCLUDE` | `include` contains a name outside the set `owner`, `host`, `attendee`. The response lists the available names |
| 400 | `INCLUDE_LIMIT_EXCEEDED` | `include` contains more than three names |
| 400 | `UNKNOWN_SELECT_FIELD` | `select` contains an unknown field. The message lists the valid names |
| 403 | `SCOPE_DENIED` | The API key does not have the `calendar` scope |
| 403 | `SCOPE_DENIED` | `include` requests a relation to an employee, but the key lacks the `user` scope. The response names the relation and the missing scope |
| 401 | `TOKEN_MISSING` | The API key has no configured tokens |

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

## See also

- [Event fields](./fields.md)
- [Update event](./update.md)
- [List events](./list.md)
- [Related data](/docs/includes)