Skip to main content
The getCalendarEvents query allows you to retrieve calendar events for authenticated users. This endpoint returns both user-specific personal events and publicly accessible events that are visible to all authenticated (non-anonymous) users.
  • You must have AUTHENTICATED scope to access calendar events. Anonymous users cannot retrieve calendar data.
  • The request should contains а valid date(s) boundary for calendar events collection.
  • The API user context must be present and valid - otherwise, access is denied.
The following arguments can be used in the query:

Available CalendarEvents

The API includes an automatic calendar events generation according to next actions:
  • Scheduled Live session
  • Available Live session spots of Live Session Bucket, that relates to started Training
Note: Additional event variations will be made available through the API in future updates.

Examples

Basic Calendar Events Query

Calendar events CTA

Calendar events may include dedicated Call to Action (CTA) objects that define the actions available to the current user, such as registering for a Live Session.
The Call to Action (CTA) object in the example above represents an available action for the calendar event within the currently authenticated user context. This action can be executed via a separate mutation call to register the user for the associated live session:
Calendar events may also include bookmark CTAs with action ID TOGGLE_BOOKMARK that allow users to bookmark/unbookmark events.

Filtering by Event Type

Pagination Example

The getCalendarEvents query supports the same advanced features as other catalog queries:

Pagination

Learn how to efficiently navigate through large sets of calendar events using cursor-based pagination.

Authentication

Understand the authentication requirements and how to properly authenticate your requests.

Error Handling

If you don’t provide a fromDate parameter, the query will return an error. Always specify a date range for optimal performance.
Common error scenarios and solutions:
  • 401 Unauthorized: Ensure you’re using a valid authentication token with AUTHENTICATED scope
  • 403 Forbidden: Verify your user account has the necessary permissions to access calendar data
  • Invalid date format: Use ISO 8601 format (e.g., “2025-07-01T00:00:00Z”)
  • Invalid date range: Ensure fromDate is before toDate
  • Future dates only: Some implementations may restrict access to events in the distant future
  • Missing cursor parameter: When using after, you must also specify first
  • Invalid cursor: Ensure cursor values are valid and not expired
  • Conflicting parameters: Don’t use both first/after and last/before together
Calendar events are cached for performance. If you don’t see recently added events, wait a few minutes for the cache to refresh, or contact support if the issue persists.