> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/api/api-calendars-and-meetings.md).

# API - Calendars and Meetings

This guide teaches how to obtain information from calendars and their respective schedules. The process is divided into two main steps: listing available calendars and querying meetings by period.

#### 1. Calendar Listing

The first step is to retrieve the list of calendars associated with the user or system. This endpoint uses a query structure to filter the desired fields.

* Endpoint: `GET /pcalendar`
* Query Parameters: `query`: Defines the return fields (e.g., id, name, isPublished, etc.).

Request Example

`GET /pcalendar?query={calendars{id,name,isPublished,createDate,userId,updateDate,publicId,userId,nextMeeting}}`

<figure><img src="/files/8ff9a1715495d66c386bcd668465ef3580e4393e" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}

### Tip:

Save the id (or publicId) of the calendar returned in this call, as it will be required for the next step.
{% endhint %}

***

#### 2. Querying Meetings by Calendar

After identifying the calendar ID, you can list all scheduled meetings within a specific time range.

* Endpoint: `GET /calendarmeeting/{calendarId}`
* URL and Query Parameters:
  * `calendarId` (Path): The numeric identifier of the calendar (e.g., 71).
  * `page`: Page index for pagination (starts at 0).
  * `from`: Start date in ISO 8601 format.

Request Example

`GET /calendarmeeting/71?page=0&from=2026-04-01T03:00:00.000Z`

<figure><img src="/files/7ce19df1b9e09220a0cb570ab5c68453f4ff7efa" alt=""><figcaption></figcaption></figure>

***

#### Flow Summary

1. Initial Call: Execute the GET on `/pcalendar` to obtain the calendar mapping.
2. Selection: The user or system chooses an id from the returned list.
3. Retrieval: Execute the GET on `/calendarmeeting/{id}` passing the time and page parameters to display the meetings.

***

#### Technical Notes

* Date Format: Make sure to send dates in UTC (Z) format to avoid time zone conflicts.
* Pagination: The parameter `page` is essential for calendars with a high volume of meetings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sprinthub.com/en/topics/api/api-calendars-and-meetings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.