How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bitrix24 Calendar API

The Calendar API from Bitrix24 — 21 operation(s) for calendar.

Bitrix24 Calendar API is one of 36 APIs that Bitrix24 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Calendar. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 21 operations across 21 paths, and defines 3 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against 2 base URLs: https://{portal}.bitrix24.com/rest, https://{host}/rest.

21 operations 21 paths 3 schemas 21 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://{installation}.bitrix24.com/rest/
Authentication
API Key, OAuth 2.0
License
Resource Areas
1

Authentication & Security 2

Bitrix24 Calendar API declares 2 security schemes for authenticating requests. An API key is passed in the query as auth (AccessToken). It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 45 scopes. By default, every request must be authenticated.

  • AccessToken — OAuth 2.0 accesstoken or incoming webhook token
  • OAuth2 — OAuth 2.0 authorization

Paths & Operations 21

Across 21 paths, the API surfaces 21 operations — 21 POST. Each is listed below with its method, path, parameters, and response codes.

Calendar 21
POST
/calendar.accessibility.get
Get User Availability from calendar.accessibility.get
calendar_accessibility_get body → 2004XX
POST
/calendar.event.add
Add Event calendar.event.add
calendar_event_add body → 2004XX
POST
/calendar.event.delete
Delete Event calendar.event.delete
calendar_event_delete body → 2004XX
POST
/calendar.event.get
Get Calendar Events List calendar.event.get
calendar_event_get body → 2004XX
POST
/calendar.event.get.nearest
Get a list of upcoming events calendar.event.get.nearest
calendar_event_get_nearest body → 2004XX
POST
/calendar.event.getbyid
Get Event by ID calendar.event.getbyid
calendar_event_getbyid body → 2004XX
POST
/calendar.event.update
Update Event calendar.event.update
calendar_event_update body → 2004XX
POST
/calendar.meeting.status.get
Get the participation status of the current user in the event calendar.meeting.status.get
calendar_meeting_status_get body → 2004XX
POST
/calendar.meeting.status.set
Set Participation Status in Event for Current User calendar.meeting.status.set
calendar_meeting_status_set body → 2004XX
POST
/calendar.resource.add
Add a new resource calendar.resource.add
calendar_resource_add body → 2004XX
POST
/calendar.resource.booking.list
Get Resource Bookings by Filter calendar.resource.booking.list
calendar_resource_booking_list body → 2004XX
POST
/calendar.resource.delete
Delete Resource calendar.resource.delete
calendar_resource_delete body → 2004XX
POST
/calendar.resource.list
Get a list of all resources calendar.resource.list
calendar_resource_list body → 2004XX
POST
/calendar.resource.update
Update resource calendar.resource.update
calendar_resource_update body → 2004XX
POST
/calendar.section.add
Add Calendar calendar.section.add
calendar_section_add body → 2004XX
POST
/calendar.section.delete
Delete Calendar calendar.section.delete
calendar_section_delete body → 2004XX
POST
/calendar.section.get
Get Calendar List calendar.section.get
calendar_section_get body → 2004XX
POST
/calendar.section.update
Update Calendar calendar.section.update
calendar_section_update body → 2004XX
POST
/calendar.settings.get
Get main calendar settings calendar.settings.get
calendar_settings_get body → 2004XX
POST
/calendar.user.settings.get
Get User Calendar Settings calendar.user.settings.get
calendar_user_settings_get body → 2004XX
POST
/calendar.user.settings.set
Set User Calendar Settings calendar.user.settings.set
calendar_user_settings_set body → 2004XX

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are BitrixTime (8 properties), BitrixResponse (4 properties), BitrixError (2 properties). Each schema is shown below with its type and property counts.

BitrixError
object
Bitrix24 REST API error response
2 properties 2 required
BitrixTime
object
Request execution time information
8 properties
BitrixResponse
object
Standard Bitrix24 REST API response
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bitrix24-calendar-api-openapi.yml Raw ↑

Other APIs Bitrix24 publishes across the network.

Bitrix24 REST API
Bitrix24 BIconnector API
Bitrix24 Business Processes API
Bitrix24 Chatbots API
Bitrix24 Chats API
Bitrix24 Company Structure API
Bitrix24 CoPilot / AI API
Bitrix24 CRM API
Bitrix24 Data Storage API
Bitrix24 Deprecated Methods API
Bitrix24 Document Generator API
Bitrix24 Drive API
Where this information came from

This is an independent, third-party profile of Bitrix24 Calendar API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.