Luma Events Scraper
Pricing
from $0.02 / 1,000 item extracteds
Luma Events Scraper
Export public Luma event titles, dates, locations, calendars, and available host and ticket details from event and discovery pages.
Luma Events Scraper
Pricing
from $0.02 / 1,000 item extracteds
Export public Luma event titles, dates, locations, calendars, and available host and ticket details from event and discovery pages.
Public Luma event, calendar, place, topic, or discover URLs. Use exact URLs for predictable targets. These pages are combined with any Location and Topic inputs, not filtered by them. If all three inputs are omitted, the Actor uses https://luma.com/discover.
Optional topic slug, such as ai. Adds a separate topic page to the sources; it does not filter Location or Luma URLs. This is not a free-text event search.
Optional place slug from an actual Luma URL, such as london. Adds a separate place page; it does not restrict the Topic source to this city. Prefer an exact Luma URL if the city name differs from its Luma slug.
Keep events starting on or after this ISO date/time, such as 2026-07-01T00:00:00Z. Events with unavailable start dates are retained. Must not be later than Start date to.
Keep events starting on or before this date/time. A date alone means midnight; use 2026-12-31T23:59:59Z to include the full day. Events with unavailable start dates are retained.
Maximum public event rows across all sources, from 1 to 10000; not a target or guarantee. Form prefill is 20, schema default is 25. Specify this explicitly for API workflows.
Keep public host names and links from listings when available. Event detail enrichment can also return host fields. No private attendee lists are collected.
Fetch individual event pages when a listing does not include a description. This improves descriptions but may make runs slower.
The form/schema default is useApifyProxy: false (direct). You may explicitly configure Apify Proxy or your own proxy URLs, used from the start for listing and detail requests; there is no automatic proxy fallback. Existing API and saved-task settings remain authoritative. If this whole field is omitted without schema defaults being applied, existing SDK-managed proxy behavior remains; pass useApifyProxy: false to explicitly opt out. Enabling managed proxies can incur proxy usage. Unsupported settings and non-boolean switches are rejected, not converted into a paid route.
{ "useApifyProxy": false}