Verify the configured Luma API key and return the authenticated user.

List events from the calendar attached to the configured API key.

Get complete details for one Luma event.

Get complete details for one event guest by guest ID, ticket key, guest key, or email. The response contains personal information and ticket-order details.

Create a Luma event. Call only after the user has explicitly confirmed the event name, date/time, timezone, and supplied details.

Update selected fields on a Luma event. Call only after showing the changes and receiving explicit confirmation.

Preview or permanently cancel and delete one Luma event. Call with confirmed=false first to show the exact event, approved guest count, and whether a refund choice is required. Cancellation is irreversible: Luma deletes the event and notifies all guests. Call with confirmed=true only after the user explicitly confirms the event and, for a paid event, whether guests should be refunded.

Add guests directly to an event with tickets and an approved, pending-approval, or waitlist status. This registers guests rather than sending a soft invite. Show the event, recipient count, status, ticket assignment, and email choice before asking for confirmation.

Send soft event invitations by email and, when linked to a Luma account, SMS. Invited people choose whether to register. Show the event, recipient count, and message before asking for confirmation.

Build a privacy-conscious audience from selected guest statuses on a source event, remove duplicate emails and anyone already on the target event, and send soft Luma invitations in batches. Call with confirmed=false first to preview aggregate counts without exposing identities; call again with confirmed=true only after explicit approval.

Approve up to 90 currently waitlisted guests per run, leaving rate-limit headroom. Large waitlists are safely resumable by rerunning the tool until resume_required is false. Call only after showing the event, waitlisted guest count, and email notification choice, then receiving explicit confirmation.

List guests for an event. Guest data may include personal information; use only for event operations requested by the user.

Count guest approval states and check-ins for an event across all guest pages without returning guest identities.