# Luma Events Scraper (`fetch_cat/luma-events-scraper`) Actor Export public Luma event titles, dates, locations, calendars, and available host and ticket details from event and discovery pages. - **URL**: https://apify.com/fetch_cat/luma-events-scraper.md - **Developed by:** [Fetch Cat](https://apify.com/fetch_cat) (community) - **Categories:** Lead generation, Marketing, Business - **Features:** Limited permissions - **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.02 / 1,000 item extracteds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README Extract public Luma event records from event, calendar, place, topic, and discovery pages. Export event links, dates, public locations, calendar information, and available host and ticket details to CSV, Excel, JSON, or an API workflow. Use Luma Events Scraper for community research, event feeds, and sponsorship prospecting. It returns events exposed by the supplied pages, not a guaranteed complete catalogue or a city-and-topic search intersection. Private attendees, RSVP answers, and login-only information are not collected. ### Quick start 1. Paste an exact public Luma page URL into **Luma URLs**. 2. Set **Maximum events** to a small limit, such as `10`. 3. Enable host fields if needed, then click **Start**. 4. Open the dataset and export the results. ```json { "startUrls": [{ "url": "https://luma.com/london?k=p" }], "maxItems": 10, "includeHosts": true, "includeEventDetails": false } ``` Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same. https://youtu.be/1OW8gOqlZbY?t=25 ### Ready-to-run examples Choose a public example to see its settings before starting a run: - [Scrape upcoming Luma events after a date](https://apify.com/fetch_cat/luma-events-scraper/examples/luma-date-filtered-events) - [Scrape London Luma events with descriptions](https://apify.com/fetch_cat/luma-events-scraper/examples/luma-london-event-details) - [Scrape Luma AI events in London](https://apify.com/fetch_cat/luma-events-scraper/examples/luma-london-ai-events) ### What you get One saved event row with a public event link, available title, dates, time zone and location text. Listing fields can include calendars, hosts, images and ticket information. Optional detail retrieval attempts missing descriptions, while absent venue or host data remains unavailable rather than inferred. ### Who is it for? - **Community researchers** reviewing events exposed by known public pages. - **Newsletter and directory editors** preparing source-linked event selections. - **Partnership researchers** following public organizer and calendar references. - **Data teams** importing dated event snapshots for their own comparisons. ### How you can use the data - **Prepare a London event shortlist.** Use the existing London page with a ten-event cap, listing hosts on and optional details off. Keep eventUrl, available dates, timezone and locationName for editorial checking rather than assuming every event has a public physical venue. - **Add useful descriptions when exposed.** Turn on optional details for the same small source when your newsletter needs context. A failed detail attempt retains the listing record, and the enrichment can make sourceUrl point at the event page. - **Combine sources without assuming an intersection.** An exact page, topic source and location source contribute combined events. A topic query plus London is not a promise of only London AI events. Preserve source references and review your own selection. - **Compare your own dated event exports.** Use eventUrl as a join key and keep extraction times in your destination. Inclusive date bounds use event start times, unknown dates remain eligible, and the Actor does not maintain changes or rank event popularity. ### Input settings | Setting | JSON key | Purpose | | --- | --- | --- | | Luma URLs | `startUrls` | Exact public pages to read. | | Topic / category query | `query` | Adds a topic source, not a free-text search or city filter. | | Location | `location` | Adds a place source using a Luma slug. | | Start date from / to | `dateFrom`, `dateTo` | Inclusive event start-time bounds. | | Maximum events | `maxItems` | Total saved-row limit across sources. | | Include public host names | `includeHosts` | Keeps available listing host fields. | | Fetch event details | `includeEventDetails` | Attempts to fill missing descriptions. | | Proxy configuration | `proxyConfiguration` | Explicit proxy settings. Form default is disabled. | The input form explains defaults and detailed behavior. All source fields are optional. If none is supplied, the Actor reads Luma Discover. When multiple source fields are supplied, their events are combined and duplicate event URLs are skipped. Results retain source order. No date or popularity sorting is applied. #### Example inputs Use the Quick start input as a small first run. Adjust the fields described above for your own data. ### Output data Each dataset row represents an event. Missing source information is generally `null` or an empty array. This synthetic example illustrates the shape only. It is not an extracted event: ```json { "eventUrl": "https://luma.com/example-event", "eventId": null, "eventTitle": "Example event", "eventDescription": null, "startDate": null, "endDate": null, "timezone": null, "locationName": null, "address": null, "isOnline": false, "hostNames": [], "hostUrls": [], "calendarName": null, "calendarUrl": null, "imageUrl": null, "tags": [], "priceText": null, "registrationStatus": null, "sourceUrl": "https://luma.com/discover", "scrapedAt": "2026-10-25T00:00:00.000Z" } ``` | Fields | Meaning | | --- | --- | | `eventUrl`, `eventId`, `eventTitle` | Event link and available identity. | | `eventDescription` | Available public description. | | `startDate`, `endDate`, `timezone` | Available event timestamps and time zone. | | `locationName`, `address` | Public location text, which may be approximate or hidden. | | `isOnline` | Online indication when exposed. `false` does not verify a physical venue. | | `hostNames`, `hostUrls` | Available public host names and links. | | `calendarName`, `calendarUrl` | Available organizer calendar. | | `imageUrl`, `tags` | Available image and category labels. | | `priceText`, `registrationStatus` | Public ticket price text and registration availability. | | `sourceUrl`, `scrapedAt` | Source reference and extraction timestamp. | The key-value store also contains `RUN_SUMMARY`, with saved count, requested limit, completed and pending source counts, a cutoff reason when present, and finish time. It is a progress summary, not a per-event quality report. Detail enrichment may change a row's `sourceUrl` to its event page. #### Download your results Open your run's dataset, choose **Export** and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet. See [Apify's download and export guide](https://docs.apify.com/storage/dataset#apify-console) for the available formats and field options. ### Pricing The `start` event is charged once per run, including a run with no saved events. The `item` event applies to each event saved in the dataset. Use a small total event cap and enable optional details only when useful. See the [live Pricing tab](https://apify.com/fetch_cat/luma-events-scraper/pricing) for current rates and account-specific discounts. ### Tips for best results - **Prefer exact Luma page URLs.** Guessed city and topic slugs may identify the wrong source or no usable page. - **Start with one source and a small cap.** Combined inputs are additive rather than a city-and-topic intersection. - **Use an explicit end-of-day timestamp when needed.** A date-only upper bound means midnight. - **Keep the event time zone with its dates.** Review dates before adding events to a newsletter or calendar. - **Check pending source counts in RUN_SUMMARY.** The summary describes progress rather than each event's field completeness. ### Limits and caveats Only public Luma event information is supported. Hidden venues, private attendees, RSVP answers and login-only information are unavailable. No popularity ranking, guest-list collection or organizer contact enrichment is provided. A false isOnline value does not verify a physical venue. Exact pages, topic sources and place sources are combined, duplicate event URLs are skipped and source order is retained. Query is a topic source rather than free-text search. No source means Luma Discover. No date or popularity sorting is applied, and listing pages are not exhaustively read across every result page. The total saved-row cap does not guarantee that many events. Date filters, duplicates, exposed source records and time limits can reduce output. Date bounds are inclusive event start-time limits. Date-only upper bounds mean midnight, and events without a parseable start date remain eligible. Optional details can take longer and do not guarantee descriptions or every field. Failed detail requests retain available listing records, and host fields may still appear through detail enrichment. Public location, ticket and registration information can be missing or change. An empty successful dataset can mean no usable events were exposed or no dated records matched, but a page change can also prevent extraction. Empty output does not establish which cause applies. Access failures can fail a run, and a blocked page does not prove privacy or deletion. Larger inputs can stop with pending sources: check RUN_SUMMARY saved counts, pending counts and cutoff reason rather than claiming complete coverage. Report unexpected missing output with a public source URL and run ID. ### Automation and integrations #### Save your settings for next time Once you have an input that works for you, [save it as an Apify task](https://docs.apify.com/actors/running/tasks). This keeps your settings together so you can use them again without filling in the form from scratch. #### Run on a schedule Need fresh results regularly? You can [schedule the Actor or a saved task](https://docs.apify.com/actors/running/schedules) to run at a time that suits you. Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow. #### Send results to your other tools Use **n8n, Make or Zapier** to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the [Apify integration guides](https://docs.apify.com/integrations) for your chosen tool. For a custom connection, an [Apify webhook](https://docs.apify.com/integrations/webhooks) can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure. ### API usage Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results. The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its `defaultDatasetId` to fetch the results. For setup instructions, see Apify's [JavaScript client guide](https://docs.apify.com/api/client/js), [Python client guide](https://docs.apify.com/api/client/python) and [Actor runs API reference](https://docs.apify.com/api/v2/acts-runs-post). #### cURL ```bash curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~luma-events-scraper/runs' \ -H "Authorization: Bearer $APIFY_TOKEN" \ -H 'Content-Type: application/json' \ --data @- <<'JSON' { "startUrls": [ { "url": "https://luma.com/london?k=p" } ], "maxItems": 10, "includeHosts": true, "includeEventDetails": false } JSON ``` #### Node.js ```javascript import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: process.env.APIFY_TOKEN }); const run = await client.actor('fetch_cat/luma-events-scraper').call({ "startUrls": [ { "url": "https://luma.com/london?k=p" } ], "maxItems": 10, "includeHosts": true, "includeEventDetails": false }); const { items } = await client.dataset(run.defaultDatasetId).listItems(); console.log(items); ``` #### Python ```python import os from apify_client import ApifyClient client = ApifyClient(os.environ['APIFY_TOKEN']) run = client.actor('fetch_cat/luma-events-scraper').call(run_input={'startUrls': [{'url': 'https://luma.com/london?k=p'}], 'maxItems': 10, 'includeHosts': True, 'includeEventDetails': False}) print(client.dataset(run['defaultDatasetId']).list_items().items) ``` ### MCP and AI agents You can ask your AI assistant to collect data with **Luma Events Scraper** and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes. Connect your assistant through the [Apify MCP server](https://mcp.apify.com/). MCP gives your assistant a way to find this scraper, run it and read the results. Follow the [official setup and sign-in guide](https://docs.apify.com/mcp) for your app. #### Easier setup with an Apify plugin If you use a supported coding assistant, the [official Apify plugin](https://docs.apify.com/agents/plugins) can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app. #### Use Apify AI in Console Prefer to keep everything in Apify? Open [Apify AI in Console](https://docs.apify.com/account/apify-ai) and ask it to find Fetch Cat's **Luma Events Scraper**. You can describe the data you want and ask questions about the results. Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply. #### Choose your assistant - **Claude and Claude Code (Anthropic):** [Apify setup guide](https://docs.apify.com/integrations/claude). - **ChatGPT and Codex (OpenAI):** [Apify setup guides](https://docs.apify.com/integrations/openai). - **Grok Bot (xAI):** [Apify plugin guide](https://docs.apify.com/integrations/grok-bot). - **Gemini CLI (Google):** [MCP server setup guide](https://geminicli.com/docs/tools/mcp-server/). Use the server URL below with the HTTP configuration supported by Gemini CLI. #### Connect just this scraper To keep your setup focused on this scraper, add this server configuration to a compatible MCP client: ```json { "mcpServers": { "apify": { "url": "https://mcp.apify.com?tools=fetch_cat/luma-events-scraper" } } } ``` Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format. #### Use Apify's general server Already connected to the general Apify MCP server at `https://mcp.apify.com`? You can use it to find this scraper without adding another server. Ask your assistant to use **Luma Events Scraper** by Fetch Cat, or give it the identifier `fetch_cat/luma-events-scraper`. Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service. #### Example requests - “Use Fetch Cat’s Luma Events Scraper to collect up to 5 events from https://luma.com/london?k=p with listing hosts enabled and event details off. Keep event links, dates, time zones and available location text for my own London shortlist.” - “Collect up to 5 events from https://luma.com/london?k=p with listing hosts and optional descriptions enabled. Keep available calendar and host links, and mark missing descriptions or venue information rather than filling them in.” - “Retrieve up to 5 events from https://luma.com/london?k=p starting on or after 1 October 2026 at midnight UTC, with details off. Retain unknown dates as uncertain and check the summary for pending sources before describing coverage.” Normal Apify charges apply. Check the [live Pricing tab](https://apify.com/fetch_cat/luma-events-scraper/pricing) before asking your assistant to run a larger batch. ### Pay with x402 If your AI agent has a funded wallet, it can pay for Apify usage through [x402](https://docs.apify.com/integrations/x402). This experimental option lets an agent use Apify without a conventional account. [Apify AGI](https://agi.apify.com/) provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection. Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability. Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration. #### Other ways for agents to pay Apify also supports **MPP** for prepaid access through AGI and **Skyfire** for eligible Actors. If your agent already uses one of these, see the [agentic payment guide](https://docs.apify.com/agents/payments) to choose the right setup. ### FAQ #### Is this a Luma events API alternative? It provides structured public page data through Apify's API. It is not Luma's official API and does not access private registration or attendee information. #### Can I export Luma events to CSV or JSON? Yes. Open the run's dataset to export supported formats, including CSV, Excel, and JSON, or retrieve rows through the Apify API. #### Why are descriptions or host fields missing? The source may not expose them. Enable `includeHosts` for listing hosts and `includeEventDetails` to attempt missing descriptions. Neither setting guarantees complete details. #### Why did I get fewer events than requested? `maxItems` is a ceiling. Available source records, date filters, duplicates, and time limits affect the saved count. Inspect `RUN_SUMMARY` for pending sources or a cutoff reason. ### Related Actors - [Meetup Events Scraper](https://apify.com/fetch_cat/meetup-events-scraper) — Public events on another community platform. - [Eventbrite Events Scraper](https://apify.com/fetch_cat/eventbrite-events-scraper) — Event discovery on Eventbrite. - [Google Maps Lead Finder](https://apify.com/fetch_cat/google-maps-lead-finder) — Venue and local-business research. - [LinkedIn Jobs Scraper](https://apify.com/fetch_cat/linkedin-jobs-scraper) — Hiring-market research around communities. - [Website Content Crawler Lite](https://apify.com/fetch_cat/website-content-crawler-lite) — Read public organizer websites for further context. ### Support and feedback For custom additions or integrations, email . Found an error or have a feature request? [Open an issue](https://apify.com/fetch_cat/luma-events-scraper/issues) with the run URL, a non-sensitive input example and what you expected. Need help sharing it? See [Apify’s guide to sharing a run when reporting an issue](https://docs.apify.com/account/collaboration/general-resource-access#automatically-sharing-runs-via-actor-issues). Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead. Tried this scraper? We'd love to hear how it worked for you. [Leave a review](https://apify.com/fetch_cat/luma-events-scraper/reviews) to help others choose the right tool and help us improve it. Your feedback means a lot to us. Made with care for curious people, AI agents and the possibilities in data. ♥ # Changelog This Actor's version history is a separate document: https://apify.com/fetch_cat/luma-events-scraper/changelog.md # Actor input Schema ## `startUrls` (type: `array`): 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. ## `query` (type: `string`): 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. ## `location` (type: `string`): 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. ## `dateFrom` (type: `string`): 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. ## `dateTo` (type: `string`): 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. ## `maxItems` (type: `integer`): 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. ## `includeHosts` (type: `boolean`): Keep public host names and links from listings when available. Event detail enrichment can also return host fields. No private attendee lists are collected. ## `includeEventDetails` (type: `boolean`): Fetch individual event pages when a listing does not include a description. This improves descriptions but may make runs slower. ## `proxyConfiguration` (type: `object`): 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. ## Actor input object example ```json { "startUrls": [ { "url": "https://luma.com/london?k=p" } ], "query": "ai", "location": "london", "maxItems": 20, "includeHosts": true, "includeEventDetails": false, "proxyConfiguration": { "useApifyProxy": false } } ``` # Actor output Schema ## `summary` (type: `string`): No description ## `overview` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "startUrls": [ { "url": "https://luma.com/london?k=p" } ], "query": "ai", "location": "london", "maxItems": 20 }; // Run the Actor and wait for it to finish const run = await client.actor("fetch_cat/luma-events-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "startUrls": [{ "url": "https://luma.com/london?k=p" }], "query": "ai", "location": "london", "maxItems": 20, } # Run the Actor and wait for it to finish run = client.actor("fetch_cat/luma-events-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "startUrls": [ { "url": "https://luma.com/london?k=p" } ], "query": "ai", "location": "london", "maxItems": 20 }' | apify call fetch_cat/luma-events-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,fetch_cat/luma-events-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/7cCZDXfBtRfT4zPIn/builds/ANEf1FFSYAwQKLa2P/openapi.json