> ## 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.

# events_cancel

> Cancel an event. You must first call /events/cancel/request to get a cancellation_token, then pass it here. This is irreversible — the event will be deleted, all guests will be notified, and refunds will be processed if should_refund is true. For paid events, you must specify should_refund.

POST`https://public-api.luma.com/v1/events/cancel`

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

from charter.packs import luma

result = asyncio.run(luma.events_cancel.ainvoke({"eventId": ..., "cancellationToken": ...}))
```

## Body

| Field | Type | Description |
| - | - | - |
| `eventId` \* | `string` | Event ID, this usually starts with evt- |
| `cancellationToken` \* | `string` | The cancellation token returned from the request endpoint. |
| `shouldRefund` | `boolean` | Whether to refund paid guests. Required if the event has paid guests. |


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