---
title: "List meeting session events"
method: GET
path: "/meeting_sessions/{id}/events"
tags: ["Meeting Session Data"]
---

# List meeting session events

`GET /meeting_sessions/{id}/events`

Returns stored events ordered by ascending `seq`. To continue, pass the last returned item's `seq` as `after`. An empty page means no later stored events existed at read time; this operation returns no separate next-page cursor. Default `limit` is 100 and maximum is 1,000.

## Path parameters

- `id` string, required

## Query parameters

- `after` integer
- `limit` integer

## Response `200`

Successful response with a list of meeting session events.

- MeetingSessionEventListResponse
  - `data` MeetingSessionEvent[], required
    - `occurred_at` string, date-time, required
    - `payload` object, required
    - `seq` integer, required
    - `type` string, required

## Other responses

- `400` — Bad Request
- `401` — Unauthorized. On api.telnyx.com, authentication is enforced by the API gateway before the request reaches the Meeting service, so a missing or invalid API key returns the standard Telnyx error envelope (`{"errors": [{"code": "10009", ...}]}`) rather than the single-`error` shape below.
- `403` — The authenticated credential is not permitted to perform this operation.
- `404` — Not Found
- `429` — Authentication is temporarily overloaded. Retry after the number of seconds in `Retry-After`.
- `500` — Internal Server Error
- `503` — Authentication is temporarily unavailable.

---

[API](https://skmtc.net/team-telnyx/apis/telnyx-api-2.md) · [All operations](https://skmtc.net/team-telnyx/apis/telnyx-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/team-telnyx/telnyx-api-2/revisions/3fdc16374d70/schema)