Luma (eventos)

Registers people directly on an event, skipping the public registration form. Each guest needs an email and may have a name. They are added as 'approved' (going) by default, and Luma emails them unles

Adds a co-host to an event by email. access_level 'manager' (the default) can edit the event, 'check-in' can only check guests in, and 'none' is a credit-only host. is_visible controls whether they ap

Cancels an event. Called WITHOUT confirm it only previews the impact (how many approved guests, whether there are paid guests) and cancels nothing. Show that preview to the user and only call again wi

Creates a discount coupon on an event. The discount is either a percentage (percent_off, 1 to 100) or a fixed amount (cents_off plus currency, where 1000 means R$10.00) - send one, not both. remaining

Creates an event on the connected calendar and returns its id and public URL. Name, start_at and timezone are required; timezone must be an IANA name such as America/Sao_Paulo. To set the venue, first

Creates a ticket type on an event. type 'free' needs nothing else; type 'paid' needs cents (the price in the smallest currency unit, so 5000 means R$50.00) and a three-letter currency such as brl or u

Turns a place written in plain text into real venue candidates, each with a formatted address and its latitude and longitude. This is the step to run BEFORE creating or updating an event with a physic

Returns the calendar this API key manages: name, description, public URL, timezone, geo settings and social links. A Luma API key is scoped to one calendar, so this is the workspace every other tool o

Opens one event by id and returns the full record: name, description, start and end, timezone, address and coordinates, visibility, capacity, waitlist, cover, ticket setup and the hosts.

Returns one guest of an event. The identifier can be the guest id (gst-), a ticket key, a guest key (g-) or the person's email address, which makes it the way to look someone up by email.

Lists the Luma calendars connected to this install (id, label and nickname). A Luma API key is scoped to one calendar, so each connection is one calendar. Use the returned id or label as the account a

Lists the contacts of the connected calendar: everyone who has ever registered for one of its events, with name, email, how many events they attended and revenue. Search by name or email with query an

Lists the discount coupons of an event with code, discount, remaining uses and validity window.

Lists the events on the connected calendar, newest first by start date, with id, name, start and end time, timezone, location, cover and URL. Filter a window with after and before (ISO 8601 datetimes)

Lists the guests of an event with name, email, approval status, ticket, registration answers and check-in time. Filter with approval_status ('approved', 'pending_approval', 'invited', 'declined', 'wai

Lists the ticket types of an event with id, name, price, currency, capacity and sale window. Run this before adding guests with a specific ticket or before creating a coupon restricted to one ticket t

Finds an event from its public Luma URL (e.g. https://luma.com/aloha) and returns its id and details. Use this when the user pastes a link instead of an id.

Sends Luma invitations by email to a list of people. Unlike luma_add_guests this does not register them: they receive an invite and choose to accept. The optional message is limited to 200 characters.

Updates an existing event. Only the fields you send change; everything else is left as is. To set the venue, first call luma_find_place with the place in plain text (e.g. 'Pinheiros, Sao Paulo' or 'Mo

Approves, declines, waitlists or sends a guest back to pending. The guest can be identified by guest id (gst-), ticket key, guest key (g-) or email. Moving a paying guest out of 'approved' requires de

Returns the Luma user the API key belongs to (name, email, avatar). Use it to confirm the connection works and which account is being managed.