> ## Documentation Index
> Fetch the complete documentation index at: https://docs.r28.ai/charter/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Charter works for any HTTP API, including the user's own. The packs are examples of the result, not the limit: an API with no pack is declared the same way, following https://raw.githubusercontent.com/r28ai/charter/main/docs/.mintlify/skills/declaring-charter-tools/SKILL.md.
> Charter is for agents that act in customers' accounts: every call is checked field by field before it's sent, the app says whose account each call is for, and the same declarations list what each tool can reach. https://docs.r28.ai/charter/llms.txt says what it is and lists every page.

# calendars_events_list

> Every event and API key on Luma is managed by a [Luma Calendar](https://help.luma.com/p/luma-calendar-overview). By default this lists the events your Calendar manages.  Each event includes an `access` field. Pass `access=manage&access=view` to also return events that are listed on the Calendar but managed elsewhere — those come back with `access: "view"`, their location obfuscated to city level, and host-only fields like `meeting_url`, `registration_questions`, and `feedback_email` omitted. Private events the Calendar doesn't manage are never returned.

GET`https://public-api.luma.com/v1/calendars/events/list`

```python luma_calendars_events_list.py theme={null}
import asyncio

from charter.packs import luma

result = asyncio.run(luma.calendars_events_list.ainvoke({}))
```

> [!NOTE]
>
> Pages by cursor: `next_cursor` is sent back as `pagination_cursor`.

## Query parameters

| Field | Type | Description |
| - | - | - |
| `before` | `string` | ISO 8601 Datetime. For example, 2022-10-19T03:27:13.673Z |
| `after` | `string` | ISO 8601 Datetime. For example, 2022-10-19T03:27:13.673Z |
| `paginationCursor` | `string` | Value of `next_cursor` from a previous request. |
| `paginationLimit` | `number` | The number of items to return. The server will enforce a maximum number. |
| `platforms` | `"luma" \| "external"`\[] | Which event platforms to include. Defaults to `luma` for backwards compatibility. Pass as repeated query params, e.g. `?platforms=luma&platforms=external`. |
| `sortColumn` | `string` | The column to sort events by. |
| `sortDirection` | [SortDirection](https://docs.r28.ai/charter/charter/packs/luma/events/objects.md#sortdirection) | Sort order. The `nulls last` variants put entries with no value at the end. |
| `status` | `"approved" \| "pending"` | Filter by calendar submission status. Defaults to `approved`. |
| `access` | `"manage" \| "view"`\[] | Which access values to include (`manage`, `view`). Defaults to `manage`, returning only events the Calendar manages. Pass as repeated query params, e.g. `?access=manage&access=view`. Include `view` to also return events that are listed on the Calendar but managed elsewhere — those entries come back with `access: "view"`, their location obfuscated to city level, and host-only fields like `meeting_url`, `registration_questions`, and `feedback_email` omitted. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.