Meetings API

Bulk Retrieval of Meetings

To perform bulk data retrieval of meetings, it is necessary to use the following endpoint:

GET /api/v2/meetings/export

This endpoint provides access to meeting records within a specific event, supporting pagination and advanced filtering. Each record in the response corresponds to one participant in a meeting. Use the Meeting ID to group participants into the same meeting.

Available Query Parameters

Parameter	Type	Required	Description
`event_id`	integer	Yes	Unique identifier of the event.
`page`	integer	No	Page number of the results (default: 1).
`per_page`	integer	No	Number of results per page (default: 100, max: 500).
`account_id`	integer	No	Filter by specific account ID.
`time_from`	integer	No	Unix timestamp to filter by appointment (scheduled) start time.
`time_to`	integer	No	Unix timestamp to filter by appointment (scheduled) end time.
`created_from`	integer	No	Unix timestamp to filter meetings by their creation time.
`created_to`	integer	No	Upper limit for the `created_from` filter.
`last_modified_from`	integer	No	Unix timestamp to filter by last modification time.
`last_modified_to`	integer	No	Upper limit for the `last_modified_from` filter.
`order`	string	No	Result ordering: `ASC` or `DESC` (default: `ASC`).
`order_by`	string	No	Field to order results by: `account_id` or `time`.

Filtering Strategy & Parameter Usage

Some fields in the meeting response may appear similar but serve distinct purposes. Understanding these differences is crucial when defining a strategy for syncing or querying meetings effectively:

✅ Appointment Date & Time

Represent when the meeting is scheduled to happen.
Useful for organizing or displaying meetings in a timeline.
Not recommended for filtering when trying to retrieve newly created meetings.

⚠️ Creation Date & Time

Indicate when the meeting was created.
Filtering by creation date based on this field is less effective, especially in short events with a high number of meetings.

✅ Recommended: Use created_from / created_to

Filter meetings based on when they were created in the system (not when they are scheduled to occur).
Best suited for daily syncs or incremental exports.

✅ Use last_modified_from / last_modified_to

Filter only those meetings that were updated, such as rescheduled, confirmed, or canceled.
Ideal for maintaining a real-time or near-real-time mirror of your meetings data.

Suggested Sync Workflow

Initial Export: Start with a full export using only event_id, per_page, and pagination.
Store Reference Timestamps: Keep track of the latest Creation Time and Last Modified values.
Incremental Sync:
- Use created_from to fetch newly created meetings.
- Use last_modified_from to fetch updates to existing ones.

This strategy ensures performance efficiency and accurate data replication across systems.