# Luma Events Scraper (`fetch_cat/luma-events-scraper`) Actor Scrape public Luma events, calendars, hosts, dates, locations, prices, and registration status for event intelligence workflows. - **URL**: https://apify.com/fetch\_cat/luma-events-scraper.md - **Developed by:** [Hanna Nosova](https://apify.com/fetch_cat) (community) - **Categories:** Lead generation, Marketing, Business - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.03 / 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. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. 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. Actors are written with capital "A". ## 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. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js/docs.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python/docs.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## Luma Events Scraper Extract public event data from Luma pages, calendars, places, and topic listings. Use it to monitor upcoming events, discover community calendars, enrich lead lists, and build local event feeds from publicly visible Luma information. ### What does Luma Events Scraper do? Luma Events Scraper collects public event records from Luma. It can start from public event pages, city/place pages, calendar pages, topic pages, and discovery-style pages. Each saved row represents one public Luma event. The actor returns event URLs, titles, dates, time zones, public location details, organizer calendar information, public hosts, images, prices, registration status, and scrape metadata. It does not collect private attendees, RSVP answers, hidden registration data, or information that requires logging in. ### Who is it for? Event marketers use it to track communities that overlap with their audience. Community managers use it to monitor comparable meetups and calendars. Startup and VC teams use it to discover founder, AI, tech, climate, and ecosystem events. Sales teams use it to find sponsorship, partnership, and field-marketing opportunities. Local event aggregators use it to create city calendars and newsletters. Researchers use it to map public event density by topic, city, host, or calendar. ### Why use this actor? ✅ Scrape public Luma event data without building your own parser. ✅ Use city, topic, calendar, discover, or individual event URLs. ✅ Export clean rows to JSON, CSV, Excel, XML, RSS, or API integrations. ✅ Keep runs small for monitoring or scale up for larger event discovery workflows. ✅ Avoid private attendee data and focus on public event metadata. ### What data can you extract? | Field | Description | | --- | --- | | `eventUrl` | Public Luma event URL | | `eventId` | Luma event API ID when available | | `eventTitle` | Event name | | `eventDescription` | Public event description when available | | `startDate` | Event start date/time in ISO format | | `endDate` | Event end date/time in ISO format | | `timezone` | Event timezone | | `locationName` | Public city/place name | | `address` | Public or obfuscated address text visible on Luma | | `isOnline` | Whether the event is online | | `hostNames` | Public host names when visible | | `hostUrls` | Public host links when visible | | `calendarName` | Luma calendar / organizer name | | `calendarUrl` | Public calendar URL | | `imageUrl` | Event image URL | | `tags` | Public categories/tags when available | | `priceText` | Free/paid price text | | `registrationStatus` | Registration availability or sold-out status | | `sourceUrl` | URL that produced the row | | `scrapedAt` | Timestamp of extraction | ### Pricing This Actor uses Apify pay-per-event pricing. The prices below come from the current Actor pricing configuration. Apify public plans map to Store discount tiers, so the table shows both the user-facing plan context and the pricing tier name. The final price shown in Apify depends on the user account plan and any custom agreement. | Event | What is charged | Free | Bronze | Silver | Gold | Platinum | Diamond | | --- | --- | ---: | ---: | ---: | ---: | ---: | ---: | | `start` | One-time fee charged when a run starts. Covers fixed startup cost. | $0.005 | $0.005 | $0.005 | $0.005 | $0.005 | $0.005 | | `item` | Charged per item extracted. | $0.000036271 | $0.000031540 | $0.000024601 | $0.000018924 | $0.000012616 | $0.000008831 | Apify may also charge platform usage for compute, storage, proxies, or data transfer outside this Actor pricing. Check the Actor run and the Apify Pricing tab for the exact cost shown to your account. ### How to scrape Luma events 1. Open the actor on Apify. 2. Add one or more public Luma URLs. 3. Optionally set a topic query such as `ai` or a location such as `london`. 4. Set `maxItems` to the number of events you want. 5. Choose whether to include public host names. 6. Turn on event detail enrichment if you need descriptions from individual event pages. 7. Click **Start**. 8. Export the dataset or connect it to your workflow. ### Input settings | JSON key | Type | Description | | --- | --- | --- | | `startUrls` | array | Public Luma event, calendar, place, category, or discover URLs. | | `query` | string | Optional topic/category such as `ai`, `tech`, or `climate`. | | `location` | string | Optional city or place slug such as `london` or `san-francisco`. | | `dateFrom` | string | Keep events starting on or after this ISO date or datetime. | | `dateTo` | string | Keep events starting on or before this ISO date or datetime. | | `maxItems` | integer | Maximum number of event rows to save. | | `includeHosts` | boolean | Include public host names and links when visible. | | `includeEventDetails` | boolean | Fetch event pages when more description details are needed. | | `proxyConfiguration` | object | Optional Apify Proxy settings; default is no proxy. | ### Input options #### Luma URLs Use `startUrls` for exact public Luma URLs. Examples: - `https://luma.com/london?k=p` - `https://luma.com/ai?k=t` - `https://luma.com/claw?k=c` - `https://luma.com/your-event-slug` #### Topic query Use `query` for a topic/category such as `ai`, `tech`, `climate`, `food`, `wellness`, or `crypto`. #### Location Use `location` for a city/place slug such as `london`, `berlin`, `paris`, `amsterdam`, or `san-francisco`. #### Date filters Use `dateFrom` and `dateTo` to keep events inside a date window. Use ISO dates such as `2026-07-01` or `2026-12-31T23:59:59Z`. #### Maximum events Use `maxItems` to control dataset size and cost. #### Host fields Use `includeHosts` to include public host names and links when visible. #### Detail enrichment Use `includeEventDetails` when listing pages do not contain descriptions and you want the actor to fetch individual event pages. ### Example input ```json { "startUrls": [ { "url": "https://luma.com/london?k=p" } ], "query": "ai", "location": "london", "maxItems": 25, "includeHosts": true, "includeEventDetails": false } ```` ### Example output ```json { "eventUrl": "https://luma.com/example-event", "eventId": "evt-example", "eventTitle": "AI Founders Meetup", "eventDescription": "Public event description...", "startDate": "2026-07-15T18:00:00.000Z", "endDate": "2026-07-15T20:00:00.000Z", "timezone": "Europe/London", "locationName": "London, United Kingdom", "address": "London, United Kingdom", "isOnline": false, "hostNames": ["Example Host"], "hostUrls": [], "calendarName": "Example Calendar", "calendarUrl": "https://luma.com/example-calendar", "imageUrl": "https://images.lumacdn.com/example.png", "tags": ["AI"], "priceText": "Free", "registrationStatus": "open", "sourceUrl": "https://luma.com/london?k=p", "scrapedAt": "2026-07-05T09:00:00.000Z" } ``` ### Tips for better results Start with specific Luma URLs whenever possible. Use city pages for local event discovery. Use calendar pages when you already know the organizer you want to monitor. Use topic pages for market mapping. Keep `includeEventDetails` off for fast listing runs. Turn `includeEventDetails` on when descriptions are important. Use date filters to remove past or out-of-window events. Keep `maxItems` low during setup and increase it after checking the output. ### Integrations Send new Luma events to Google Sheets for sponsorship tracking. Push event rows to Airtable for community calendar workflows. Use Make or Zapier to alert a Slack channel when new events appear. Export CSV files for sales research and account planning. Feed dataset items into enrichment tools for organizer research. Create recurring Apify schedules to monitor cities or calendars weekly. ### API usage #### Node.js ```js import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: process.env.APIFY_TOKEN }); const run = await client.actor('/luma-events-scraper').call({ startUrls: [{ url: 'https://luma.com/london?k=p' }], maxItems: 25, }); console.log(run.defaultDatasetId); ``` #### Python ```python from apify_client import ApifyClient client = ApifyClient('YOUR_APIFY_TOKEN') run = client.actor('/luma-events-scraper').call(run_input={ 'startUrls': [{'url': 'https://luma.com/london?k=p'}], 'maxItems': 25, }) print(run['defaultDatasetId']) ``` #### cURL ```bash curl -X POST 'https://api.apify.com/v2/acts/~luma-events-scraper/runs?token=YOUR_APIFY_TOKEN' \ -H 'Content-Type: application/json' \ -d '{"startUrls":[{"url":"https://luma.com/london?k=p"}],"maxItems":25}' ``` ### Use with AI agents via MCP Luma Events Scraper is available as a tool for AI assistants that support the Model Context Protocol (MCP). Add the Apify MCP server to your AI client. This gives you access to all Apify actors, including `/luma-events-scraper`. **Setup for Claude Code:** ```bash claude mcp add --transport http apify "https://mcp.apify.com" ``` **Setup for Claude Desktop, Cursor, or VS Code:** ```json { "mcpServers": { "apify": { "url": "https://mcp.apify.com" } } } ``` Your AI assistant will authenticate with your Apify account on first use. Example prompts: - "Use `/luma-events-scraper` to find the next 20 public Luma AI events in London." - "Scrape this Luma calendar and summarize the host names, dates, and locations." - "Create a table of upcoming Luma events from these city pages." ### Scheduling You can schedule this actor to run daily, weekly, or monthly. For monitoring, use a stable set of calendar or city URLs. Export the dataset after each run or connect the output to another actor. ### Proxy and reliability notes Most public Luma pages work without a proxy. If your network is blocked, enable Apify Proxy in the input. Keep large recurring runs conservative and use specific source URLs. ### Limitations The actor only extracts data that is publicly visible on Luma pages. Some private venue details may be intentionally hidden by Luma or the event host. Some listing pages may expose fewer event fields than individual event pages. Dynamic search behavior can change as Luma updates its website. ### Legality and ethical use This actor is designed for public event metadata. Do not use it to collect private attendee data or bypass access controls. Respect Luma's terms, applicable privacy laws, and event host expectations. Use the data for legitimate research, monitoring, aggregation, and business workflows. ### FAQ and troubleshooting #### Why are host fields empty? Some Luma pages do not expose public host links, or you may have disabled `includeHosts`. #### Why is the exact venue missing? Many Luma hosts hide venue addresses until registration is approved. The actor only returns public location text. #### Why did I get fewer events than `maxItems`? The source page may contain fewer public events, or date filters may remove some rows. #### How do I get descriptions? Turn on `includeEventDetails` so the actor fetches individual event pages when needed. ### Related scrapers Explore related Apify actors for research and enrichment workflows: - [Google Maps Lead Finder](https://apify.com/fetch_cat/google-maps-lead-finder) for local venue and sponsor prospecting. - [LinkedIn Jobs Scraper](https://apify.com/fetch_cat/linkedin-jobs-scraper) for hiring-market signals around event communities. - [Website Content Crawler Lite](https://apify.com/fetch_cat/website-content-crawler-lite) for public website enrichment after event discovery. Use Luma Events Scraper alongside enrichment actors to build richer event intelligence pipelines. ### Support If a public Luma page does not extract as expected, open an Apify issue and include: - the input JSON you used; - the reproducible public URL that should return events; - the expected output fields or event count; - the actual output or run ID you received. Include whether the page is a city, topic, calendar, or event page. # Actor input Schema ## `startUrls` (type: `array`): Public Luma event, calendar, place, category, or discover URLs to scrape. Examples: https://luma.com/london?k=p or https://luma.com/claw?k=c ## `query` (type: `string`): Optional Luma topic to scrape, such as ai, tech, climate, food, wellness, or crypto. ## `location` (type: `string`): Optional Luma place/city slug or city name, such as london, berlin, paris, new-york, or san-francisco. ## `dateFrom` (type: `string`): Only keep events starting on or after this date/time. Use ISO format, for example 2026-07-01 or 2026-07-01T00:00:00Z. ## `dateTo` (type: `string`): Only keep events starting on or before this date/time. Use ISO format, for example 2026-12-31 or 2026-12-31T23:59:59Z. ## `maxItems` (type: `integer`): Maximum number of public Luma events to save. ## `includeHosts` (type: `boolean`): Include public host names and host links when Luma exposes them on event pages. Attendee lists are never scraped. ## `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`): Optional proxy settings. Usually not needed for public Luma pages; leave default unless requests are blocked. ## 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 ## `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("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).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": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=fetch_cat/luma-events-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Luma Events Scraper", "description": "Scrape public Luma events, calendars, hosts, dates, locations, prices, and registration status for event intelligence workflows.", "version": "0.1", "x-build-id": "DQRWs1PqRXyBG2TKF" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/fetch_cat~luma-events-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-fetch_cat-luma-events-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/fetch_cat~luma-events-scraper/runs": { "post": { "operationId": "runs-sync-fetch_cat-luma-events-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/fetch_cat~luma-events-scraper/run-sync": { "post": { "operationId": "run-sync-fetch_cat-luma-events-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "properties": { "startUrls": { "title": "Luma URLs", "type": "array", "description": "Public Luma event, calendar, place, category, or discover URLs to scrape. Examples: https://luma.com/london?k=p or https://luma.com/claw?k=c", "items": { "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "title": "URL of a web page", "format": "uri" } } } }, "query": { "title": "Topic / category query", "type": "string", "description": "Optional Luma topic to scrape, such as ai, tech, climate, food, wellness, or crypto." }, "location": { "title": "Location", "type": "string", "description": "Optional Luma place/city slug or city name, such as london, berlin, paris, new-york, or san-francisco." }, "dateFrom": { "title": "Start date from", "type": "string", "description": "Only keep events starting on or after this date/time. Use ISO format, for example 2026-07-01 or 2026-07-01T00:00:00Z." }, "dateTo": { "title": "Start date to", "type": "string", "description": "Only keep events starting on or before this date/time. Use ISO format, for example 2026-12-31 or 2026-12-31T23:59:59Z." }, "maxItems": { "title": "Maximum events", "minimum": 1, "maximum": 10000, "type": "integer", "description": "Maximum number of public Luma events to save.", "default": 25 }, "includeHosts": { "title": "Include public host names", "type": "boolean", "description": "Include public host names and host links when Luma exposes them on event pages. Attendee lists are never scraped.", "default": true }, "includeEventDetails": { "title": "Fetch event details", "type": "boolean", "description": "Fetch individual event pages when a listing does not include a description. This improves descriptions but may make runs slower.", "default": false }, "proxyConfiguration": { "title": "Proxy configuration", "type": "object", "description": "Optional proxy settings. Usually not needed for public Luma pages; leave default unless requests are blocked.", "default": { "useApifyProxy": false } } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```