List
To list all sessions you need to execute a GET request against the /sessions endpoint.
Since potentially there could be thousands of sessions, pagination is supported with limit, order and after arguments. Read about pagination to learn the details of it. By default maximum 100 sessions will be returned in the response.
To filter sessions from a concrete date interval use the date_start and date_end query parameters: api/v1/sessions?date_start=2024-04-03&date_end=2024-04-18
To list all sessions for a concrete room execute a GET request against the /sessions endpoint and add the room_id param. api/v1/sessions?room_id=87a5d383-9e79-44ea-b382-686e430f4ecc
You can also use: api/v1/rooms/87a5d383-9e79-44ea-b382-686e430f4ecc/sessions
If you want to retrieve the details of one concrete session, execute a GET request against the api/v1/sessions/:id endpoint
If you want to filter live sessions only (haven't ended yet), then use the live parameter: api/v1/sessions?live=true If you want to filter ended sessions only: api/v1/sessions?live=false
Request (listing all sessions)
Response (200 OK)
The total_count is the total amount of sessions that happened. It is NOT the amount of sessions in the current page returned in the data array. In the above example you have 8096 sessions in total, but in the data array there will be maximum 100 sessions (the default limit argument value).
Request (get a concrete session)
Response (200 OK)
Last updated