GET request to
/meetings returns a list of meeting sessions.
Meeting sessions are returned sorted by
start_time time in reverse chronological order.
Results can be filtered by supplying any of
Each call to this endpoint fetches a maximum of 100 meeting session objects.
See Nuts and Bolts: Pagination for how pagination works in API requests (and how to use the
starting_after query parameters).
The response body consists of two fields:
total_count field is the total number of meeting session objects that match the query, including the filtering by
timeframe_end, but ignoring pagination arguments. (In other words, if pagination arguments are supplied,
total_count could be greater than the number of meeting session objects returned by this query).
data field is a list of meeting session objects. Each meeting session object includes the
room (room name),
duration (in seconds), a boolean that describes whether the meeting is
ongoing, and a
participants object of all meeting attendees.
Granularity of timestamps
duration fields are accurate to approximately 15 seconds. We don't write a "meeting join" record into our database until a user has stayed in a room for at least 10 seconds.
In general, we try to slightly undercount usage, to make sure we're not overcharging you for meeting participant-minutes!
room argument should be a room name, and limits results to that room.
timeframe_start argument is a unix timestamp, and limits results to meeting sessions that have a
start_time greater than or equal to
timeframe_end argument is a unix timestamp, and limits results to meeting sessions that have a
start_time less than
ongoing argument is a boolean value. If set to
true, it limits results to meetings where participants are currently in the room. If set to
false, it limits the results to meetings where there are no participants remaining in the room.
no_participants argument is a boolean value. If set to
true, this endpoint won't return the participant list in each meeting. This is useful for meetings with large numbers of participants. You can use the meetings/:meeting/participants endpoint to retrieve a paginated list of participants for a given meeting.