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

> Add guests to the event. By default, guests are added with the status "Going" (approved) and receive one ticket of the default ticket type. Use the `ticket` or `tickets` parameter to specify custom ticket assignments. Get available ticket types using `/v1/events/ticket-types/list`. Use `approval_status` to add guests as pending approval or on the waitlist instead of immediately approved. Use `registration_answers` on each guest to record answers to the event's registration questions — question IDs come from the `registration_questions` field of Get Event. Guests are added in the background; the response lists any guests that will be skipped because they unsubscribed from your calendar, were removed by an admin, or blocked you.

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

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

from charter.packs import luma

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

## Body

| Field | Type | Description |
| - | - | - |
| `eventId` \* | `string` | Event ID, this usually starts with evt- |
| `guests` \* | [EventsGuestsAddGuest](https://docs.r28.ai/charter/charter/packs/luma/events/objects.md#eventsguestsaddguest)\[] | The guests to add, each by email. |
| `ticket` | [Ticket](https://docs.r28.ai/charter/charter/packs/luma/events/objects.md#ticket) | Optional. Assign a single ticket of the specified type to each guest. Cannot be used with `tickets` parameter. |
| `tickets` | [Ticket](https://docs.r28.ai/charter/charter/packs/luma/events/objects.md#ticket)\[] | Optional. Assign multiple tickets to each guest. Each guest receives all tickets in the array. Use this to add multiple tickets of the same or different types. Cannot be used with `ticket` parameter. |
| `approvalStatus` | [EventsGuestsAddApprovalStatus](https://docs.r28.ai/charter/charter/packs/luma/events/objects.md#eventsguestsaddapprovalstatus) | Optional. Status to assign to each added guest. Defaults to `approved` ("Going"). Use `pending_approval` to add guests for host review, or `waitlist` to add to the event waitlist. To send a soft invite that guests can accept, use `/v1/events/guests/send-invites` instead. |
| `sendEmail` | `boolean` | Optional. Whether Luma should email each added guest. Defaults to true. Set to false if your integration sends its own notifications. |


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