---
title: "Update Guest Status"
method: POST
path: "/v1/events/guests/update-status"
tags: ["Events"]
---

# Update Guest Status

`POST /v1/events/guests/update-status`

Update a guest’s status. Set `status` to `approved` ("Going"), `declined`, `pending_approval`, or `waitlist`. Use `should_refund` to refund a paid guest when moving them out of an approved state. Use `message` to include a personal note in the email we send the guest. To send a soft invite that guests can accept, use `/v1/events/guests/send-invites` instead.

## Request body

- object
  - `event_id` string, required — Event ID, this usually starts with evt-
  - `guest_id` string, required — Guest identifier — the guest ID (gst-), a ticket key, a guest key (g-), or the user's email.
  - `status` 'approved' | 'declined' | 'pending_approval' | 'waitlist', required
  - `should_refund` boolean — If you are moving a guest who has paid to `declined`, `waitlist`, or `pending_approval`, should we refund their payment? Defaults to false.
  - `send_email` boolean, nullable — Optional. Whether Luma should email the guest about the status change. Defaults to true. Set to false if your integration sends its own notifications.
  - `message` string, nullable — Optional. Personal message included in the email we send the guest about the status change. Max of 200 characters. Can't be combined with `send_email: false`.

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