---
title: "Add Guests"
method: POST
path: "/v1/events/guests/add"
tags: ["Events"]
---

# Add Guests

`POST /v1/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.

## Request body

- object
  - `event_id` string, required — Event ID, this usually starts with evt-
  - `guests` object[], required
    - `email` string, required
    - `name` string, nullable
    - `registration_answers` object[], nullable — Optional. The guest's answers to the event's registration questions. If the guest is already registered with answers, their existing answers are kept.
      - `question_id` string, required — ID of one of the event's registration questions. Question IDs are returned in the `registration_questions` field of Get Event.
      - `value` union, required — The guest's answer. Use a string for text-style questions (`text`, `long-text`, `dropdown`, `url`, `phone-number`, and social handles), an array of strings for `multi-select`, a boolean for `agree-check`, and an object with `company` and `job_title` for `company` questions.
        - string
        - boolean
        - string[]
        - object
          - `company` string, nullable
          - `job_title` string, nullable
  - `ticket` object, nullable — Optional. Assign a single ticket of the specified type to each guest. Cannot be used with `tickets` parameter.
    - `event_ticket_type_id` string, required
  - `tickets` object[], nullable — 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.
    - `event_ticket_type_id` string, required
  - `approval_status` 'approved' | 'pending_approval' | 'waitlist', nullable — 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.
  - `send_email` boolean, nullable — Optional. Whether Luma should email each added guest. Defaults to true. Set to false if your integration sends its own notifications.

## Response `200`

Successful response.

- object — Empty response

---

[API](https://skmtc.net/luma/apis/luma-api.md) · [All operations](https://skmtc.net/luma/apis/luma-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/luma/luma-api/revisions/12835be09062/schema)