For AI agents: markdown of this page — /docs-content-en/entities/calendar-events/get.md documentation index — /llms.txt
Get event
GET /v1/calendar-events/:id
Returns a single calendar event by identifier.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
id (path) |
number | yes | Event ID |
include (query) |
string | no | Related employees: owner, host, attendee. Details — the "Related data" section below |
Examples
curl — personal key
curl "https://vibecode.bitrix24.com/v1/calendar-events/7773" \
-H "X-Api-Key: YOUR_API_KEY"
curl — OAuth application
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
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
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
The event object with all fields — see Event fields.
Related data
Get the employees related to the event together with the event itself — the include parameter in the GET request:
GET /v1/calendar-events/7773?include=owner,host,attendee
Available includes — 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 |
attendee |
attendeeList — the invitees |
users |
Array of cards in attendeeList order. Without invitees — an empty array |
The employee card is the same as in the GET /v1/users/:id response. The relation reads an employee, so the key needs the user scope in addition to calendar. The result is in the _included field:
{
"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 }
]
}
}
}
The main fields of the event and the employee are shown. The full card — Employee fields.
Response example
{
"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:
{
"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 |
| 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.