App Logo
luma.com

Get Luma event attendees

TL;DR

Automatically get Luma event attendees on luma.com. An unofficial Luma API: get the attendees of a Luma event programmatically, from code or from an AI agent, with typed JSON in and out. Luma's official API only returns guests of events you host.

Input

slug required

The event's short Luma slug, e.g. "9n5kxo7k" from luma.com/9n5kxo7k.

max_attendees optional

Stop after roughly this many attendees instead of walking the whole roster. Omit to fetch everyone; large events run to several hundred.

Output

slug required
event_id required
attendees required
guest_count required
roster_scope required

"full" = every attendee Luma will disclose; "public_preview" = only the featured subset shown on the event page.

show_guest_list required
roster_note optional

When roster_scope is public_preview, why the full roster was not available.

my_approval_status optional

FAQ

Get the attendees of a Luma event. When the signed-in account is an approved guest and the organizer has the guest list switched on, this returns the full roster — every guest, paginated, with their public profile and social handles. Otherwise it returns the featured preview Luma shows on the event page and explains why in roster_note, so a short list is never mistaken for an empty event. Check roster_scope to tell the two apart. Returns public profile fields only — no email addresses — but it is still a list of real people, so treat the output as personal data.
Ask an AI agent connected to Reduck to run reduck/luma.com/get_event_attendees, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/luma.com/get_event_attendees
You do not need one. "Get Luma event attendees" drives the real luma.com pages in a browser, so it works whether or not luma.com offers an API for this.
Required: slug. Optional: max_attendees.
It returns slug, event_id, attendees, guest_count, roster_note, roster_scope, show_guest_list, my_approval_status.
Yes. It acts as you on luma.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the luma.com cookies saved by the Reduck extension.
It only reads. It looks things up on luma.com and changes nothing there.
Ask an AI agent connected to Reduck to run reduck/luma.com/get_event_attendees, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/luma.com/get_event_attendees
It is part of Reduck's official curated catalogue.

Start building not clicking