Update Guest Tickets

post

https://public-api.luma.com/v1/events/guests/update-tickets

Add or remove tickets from an existing guest. Added tickets are complimentary. Removed tickets are invalidated and, if should_refund is set, refunded for what the guest paid for them; otherwise no money moves. You can’t change tickets for guests with pending payment holds. Administrative ticket changes can exceed event or ticket-type capacity.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

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.

ticket_ids_to_remove

array of strings

Defaults to []

Existing ticket IDs to invalidate. At least one valid ticket must remain on the guest. Pass should_refund to refund the removed tickets.

ticket_ids_to_remove

should_refund

boolean | null

Optional. Refund each removed paid ticket for what the guest paid for it. The guest stays registered with their remaining tickets. The refund is limited to what's left on the order beyond the tickets the guest keeps, so a partial refund already issued from the dashboard isn't paid out again. Crypto payments can't be refunded this way. Defaults to false.

tickets_to_add

array of objects

Defaults to []

Complimentary tickets to grant. Each entry creates a new $0 administrative ticket, even when the ticket type is normally paid.

tickets_to_add

send_email

boolean | null

Optional. Whether Luma may email the guest about the ticket change, including the refund receipt when should_refund is set. Defaults to true and still respects their notification preferences. This only controls email — the guest still gets an in-app notification, and push follows their preferences.

Response

Language

Credentials

Header

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Successful response.