# Eventbrite Scraper: Events by City, Date & Category (`accountable_eel/eventbrite-events-lookup`) Actor Eventbrite events by city, keyword and date: name, start and end time, venue, price range, organiser and ticket status. Monitor a search for new events, price changes and sold-out events, with alerts to Slack, Discord or Telegram. No login. Searches that find nothing are free. - **URL**: https://apify.com/accountable_eel/eventbrite-events-lookup.md - **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community) - **Categories:** Lead generation, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.51 / 1,000 event returneds 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 ## Eventbrite Scraper: Events by City, Date & Category Search Eventbrite by place, keyword and date and get one row per event: **name, start and end time (with the venue's UTC offset), venue, city, category**, and, when you switch on event pages, the **ticket price range, free or paid, organiser and sold-out status**. Switch on monitoring and the actor remembers every event it has seen, so a daily run tells you which events are **new**, **repriced** or **sold out**, optionally straight into Slack, Discord or Telegram. No login, no cookies, no API key. A search that finds nothing costs nothing. ### Who uses this - **Event-lead builders and sponsors** who want every conference, meetup or expo in a city this month, with the organiser, to start outreach. - **Local-event aggregators and newsletters** that list "what's on this weekend" for a city and need fresh rows every morning. - **n8n / Make / Clay workflows** that need a clean event list from a place and a keyword, or an alert when a new event appears. ### Try it in 30 seconds Press **Start** with the pre-filled input: it searches New York, returns the first 20 events, and takes one page request. ```json { "searches": ["ny--new-york"], "maxEvents": 20 } ``` Write your own lines, one search per line, place first and an optional keyword after a bar: ```text ny--new-york everything in New York Austin, TX | startup keyword "startup" in Austin London, United Kingdom | tech keyword "tech" in London online | python online events about python https://www.eventbrite.com/d/ny--new-york/jazz/ a pasted search link ``` A place is "City, ST" for the US, "City, Country", an Eventbrite place slug (`ny--new-york`), or `online`. If Eventbrite does not know the place or the keyword, that line comes back as a free "not found" row. ### What you get One row per event: | Field | What it is | |---|---| | `eventId`, `url`, `name`, `summary` | The event, its public page and the organiser's short description | | `startAt`, `endAt`, `timezone` | Start and end with the venue's UTC offset, e.g. `2026-11-01T17:00:00-05:00` | | `venue`, `city`, `region`, `country`, `online` | Where it happens (venue name and town only, no street addresses) | | `category` | Eventbrite's category, e.g. Music, Business | | `isFree`, `minPrice`, `maxPrice`, `currency`, `ticketsAvailable`, `organizerName`, `organizerUrl` | Filled when **Fetch event pages** is on (see Limits) | | `cancelled` | Eventbrite marks the event as cancelled | | `changeType`, `previousMinPrice`, `previousMaxPrice`, `firstSeenAt` | Monitoring: `baseline`, `new-event`, `price-change`, `sold-out` or `unchanged` | | `totalMatches`, `hasMore` | How many events Eventbrite says match, and whether more exist than were returned | Filters that reach Eventbrite: place, keyword, **date range** (today, tomorrow, this weekend, next week, next 30 days, or exact start and end dates) and **online only**. Filters applied by the actor after the fetch: **free only** and **paid only** (they read each event page, so they take longer). ### Example: new events this weekend, posted to Discord Search New York for this weekend, remember what was seen, and post each new event to a Discord channel: ```json { "searches": ["ny--new-york | music"], "dateRange": "this_weekend", "maxEvents": 100, "deltaMode": true, "deltaName": "ny-music-weekend", "alertOn": "new-event", "alertOnChangeOnly": true, "notifyUrl": "https://discord.com/api/webhooks//" } ``` Run it daily on a schedule. The first run only sets the baseline (nothing is "new" yet, and nothing is posted); from the second run on, only events that were not on the search before are returned, billed and posted. The webhook link is stored encrypted and never appears in the results. ### Monitoring: new, repriced, sold out Turn on **Track events across runs** and each run compares every event with the previous run of the same search and watchlist name. **Tell me about** picks what counts: new events, price changes, sold-out events, or all three. Price changes and sold-out need the event pages, which are then fetched automatically. **Only return rows that changed** drops unchanged events from the output and the bill. **Seed silently** remembers the first run without returning it. State lives in a named store (`eventbrite-events-lookup-delta`) that keeps up to 20,000 events per watchlist. Alerts go to a Discord or Slack webhook, a Telegram bot link or any URL (JSON for n8n, Make or Zapier), at most 20 messages per run by default. A message is only sent for an event row that was actually billed, and a failed message never fails the run. ### Limits, stated plainly - **Search list vs event pages.** Eventbrite's search results carry no price, organiser or ticket status. Those come from each event's own page: turn on **Fetch event pages** (one extra request per event). Without it, `isFree`, `minPrice`, `maxPrice`, `currency`, `organizerName`, `organizerUrl` and `ticketsAvailable` are empty. The free / paid filters and price-change / sold-out alerts switch it on by themselves. - **Speed.** The actor makes at most one request per second. A search page holds 20 events, so 100 events without event pages take well under a minute. Each event page takes a few seconds more (measured 2 to 6 seconds on the residential proxy), so about 100 events with event pages fit in one run. A run stops fetching after about 9 minutes and returns what it has (`hasMore: true`). - **How many.** Up to 500 events per search and 20 searches per run. Eventbrite lists at most 1,000 events per search (50 pages of 20); with event pages, expect to reach about 100 events per run (see Speed). - **Dates.** A date window returns events that run during it, including multi-day events that started earlier. "Today" and "this weekend" are worked out from today's date in UTC. - **Places.** Eventbrite place slugs are `state--city` in the US (`ny--new-york`) and `country--city` elsewhere (`united-kingdom--london`). Outside the US, Eventbrite sends event links on the country domain (eventbrite.co.uk, .nl, .ca ...); the rows keep the link as Eventbrite gave it. - **Not collected.** No attendee lists, no comments, no emails or phone numbers, no street addresses. Category and date path pages (like `business--events`) are not read; use the keyword and date range instead. - **Proxy.** Runs use a residential proxy by default: Apify's datacenter proxy was served a bot-check page instead of results. - **Terms.** Eventbrite's terms restrict commercial use of site content. You are responsible for how you use the data. ### How to use 1. **In the Apify Console.** Open the actor page and click **Start** — the `searches` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found. 2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token: ```bash curl "https://api.apify.com/v2/acts/accountable_eel~eventbrite-events-lookup/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"searches":["ny--new-york"]}' ``` 3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required. ### Input ```json { "searches": [ "ny--new-york" ] } ``` One search per line: a place, then an optional keyword after a bar. Places: "City, ST" (US), "City, Country", an Eventbrite place slug like ny--new-york, or "online". You can also paste an Eventbrite search link (https://www.eventbrite.com/d/ny--new-york/jazz/). Up to 20 searches per run. Accepted formats: ny--new-york, ny--new-york | jazz, London, United Kingdom | tech, Austin, TX | startup, online | python, https://www.eventbrite.com/d/ny--new-york/jazz/. ### Sample output | query | found | status | searchQuery | totalMatches | hasMore | events | eventId | url | name | summary | startAt | endAt | timezone | venue | city | region | country | online | isFree | minPrice | maxPrice | currency | category | organizerName | organizerUrl | ticketsAvailable | cancelled | checkedAt | changeType | previousMinPrice | previousMaxPrice | firstSeenAt | notifyErrors | scrapedAt | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | ny--new-york | true | OK | | | | \ | | | | | | | | | | \ | | | | | | | | | | | | | | | | | | 1970-01-01T00:00:00.000Z | A miss comes back as a row with `"found": false` and is never charged. ### Pricing Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed per item only when data is actually found and returned — see `.actor/pay_per_event.json` for exact prices. A miss is never charged. ### Use it from Clay, n8n, Make, or an AI agent This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token. ```bash curl "https://api.apify.com/v2/acts/accountable_eel~eventbrite-events-lookup/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"searches":["ny--new-york"]}' ``` **n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~eventbrite-events-lookup/run-sync-get-dataset-items?token=`, Body Content Type `JSON`, JSON Body `{"searches":["ny--new-york"]}` (swap in an expression from an earlier node for a real value). **Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~eventbrite-events-lookup/run-sync-get-dataset-items?token=`, Body `{"searches":["{{search}}"]}`, mapping the row's search into the `searches` array. **MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Eventbrite Scraper | Apify" — the agent will find and run this actor. ### FAQ **Why are the price columns empty?** Eventbrite's search list has no prices. Turn on **Fetch event pages** to open each event and read its ticket range. **Why does a place come back as not found?** Eventbrite did not recognise the place slug. Use "City, ST" or "City, Country", or copy the slug from an Eventbrite search link (`/d//...`). **Can I get only free events?** Yes: **Free events only**. It reads event pages, so it scans up to five times the number of events you asked for. **Does it work from a schedule?** Yes. Save it as a Task with monitoring on and a watchlist name, then schedule it daily. # Actor input Schema ## `searches` (type: `array`): One search per line: a place, then an optional keyword after a bar. Places: "City, ST" (US), "City, Country", an Eventbrite place slug like ny--new-york, or "online". You can also paste an Eventbrite search link (https://www.eventbrite.com/d/ny--new-york/jazz/). Up to 20 searches per run. Accepted formats: ny--new-york, ny--new-york | jazz, London, United Kingdom | tech, Austin, TX | startup, online | python, https://www.eventbrite.com/d/ny--new-york/jazz/. You're only charged for the ones we actually find — a miss costs nothing. ## `maxEvents` (type: `integer`): How many events to return for each search line. Eventbrite shows 20 per page, so 100 events is 5 page requests. Up to 500. ## `dateRange` (type: `string`): Keeps only events happening in the window. "This weekend" is Saturday and Sunday (or what is left of it). Windows are worked out from today (UTC) and sent to Eventbrite as exact dates, so they match the Eventbrite site. Overridden by the start and end dates below. ## `startDate` (type: `string`): YYYY-MM-DD. With an end date, returns events running in that window and overrides "Date range". Alone, the window is that one day. ## `endDate` (type: `string`): YYYY-MM-DD. If it is before the start date, the start date is used. ## `onlineOnly` (type: `boolean`): Searches Eventbrite's online events for the keyword instead of the place. The place is ignored. ## `includeEventDetails` (type: `boolean`): Eventbrite's search list has no price, organiser or ticket status. Turn this on to open each event's page (one extra request per event, one request per second) and fill ticket prices, currency, free flag, organiser and sold-out status. Switched on automatically by the free / paid filters and by price-change and sold-out alerts. Slower: 100 events take about two minutes. ## `freeOnly` (type: `boolean`): Keeps only events whose tickets are all free. Opens each event page to know (see above), so it scans up to 5 times the number of events you asked for. ## `paidOnly` (type: `boolean`): Keeps only events with a ticket price above zero. Same scan as free-only; ignored if free-only is also on. ## `deltaMode` (type: `boolean`): Turns the actor into an event monitor. Each run compares every event with the previous run of the same search and fills in "Change since last run". Schedule it daily and combine with "Only return rows that changed" and "Send alerts to". ## `deltaName` (type: `string`): Leave empty and one is derived from your settings. Type your own name to keep one memory across changes, or to run several independent watchlists. ## `alertOn` (type: `string`): What counts as a change. The first run of a search only sets the baseline, so nothing is "new" yet. Price changes and sold-out status need the event pages, which are then fetched automatically (one request per event). ## `alertOnChangeOnly` (type: `boolean`): With monitoring on, an event with no change writes no row and is not billed. Baseline, new, price-change and sold-out events are returned. ## `skipFirstRun` (type: `boolean`): The first run of a search has nothing to compare with. Turn this on to remember its events without returning or billing them, so rows and alerts start from the second run. ## `notifyUrl` (type: `string`): Optional. After an event row is billed, each new event, price change and sold-out is posted here as one message with name, time, place, price and a link. Discord or Slack: paste the channel's webhook URL. Telegram: https://api.telegram.org/bot/sendMessage?chat_id=. Any other URL receives JSON. Messages are free, and a failed message never fails the run (the row's notifyErrors says why). Stored encrypted, never logged or written to the results. ## `notifyFormat` (type: `string`): Leave on "Detect from the link": discord.com links get Discord messages, hooks.slack.com Slack, api.telegram.org Telegram, anything else JSON. Pick one only to override that. ## `maxNotificationsPerRun` (type: `integer`): Up to 100. After this, one "more alerts" message says the rest are in the run's dataset. 0 sends only that one message. ## `testRun` (type: `boolean`): Turn this on to test your input on a small sample before running the full list. Turn it off to process everything. ## `onlyFound` (type: `boolean`): Only keep rows where something was actually found. Misses are always free, whether or not you show them here. ## `includeKeywords` (type: `array`): Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything. ## `excludeKeywords` (type: `array`): Optional. Drop any result that mentions one of these words. Leave empty to skip nothing. ## `maxResults` (type: `integer`): Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit. ## `columns` (type: `array`): Choose which pieces of information to include in each result row. All are included by default. ## `expandRows` (type: `boolean`): When on, each event found gets its own row instead of being grouped under its search. You're still only charged once per search, no matter how many rows it produces. ## `maxConcurrency` (type: `integer`): Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady. ## `proxyConfiguration` (type: `object`): Apify Proxy config. Residential recommended for anti-bot-sensitive targets. ## Actor input object example ```json { "searches": [ "ny--new-york" ], "maxEvents": 20, "dateRange": "any", "startDate": "", "endDate": "", "onlineOnly": false, "includeEventDetails": false, "freeOnly": false, "paidOnly": false, "deltaMode": false, "deltaName": "", "alertOn": "new-event", "alertOnChangeOnly": false, "skipFirstRun": false, "notifyFormat": "auto", "maxNotificationsPerRun": 20, "testRun": false, "onlyFound": false, "includeKeywords": [], "excludeKeywords": [], "columns": [ "searchQuery", "totalMatches", "hasMore", "events", "eventId", "url", "name", "summary", "startAt", "endAt", "timezone", "venue", "city", "region", "country", "online", "isFree", "minPrice", "maxPrice", "currency", "category", "organizerName", "organizerUrl", "ticketsAvailable", "cancelled", "checkedAt", "changeType", "previousMinPrice", "previousMaxPrice", "firstSeenAt", "notifyErrors" ], "expandRows": true, "maxConcurrency": 1, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } } ``` # Actor output Schema ## `results` (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 = { "searches": [ "ny--new-york" ], "includeKeywords": [], "excludeKeywords": [] }; // Run the Actor and wait for it to finish const run = await client.actor("accountable_eel/eventbrite-events-lookup").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 = { "searches": ["ny--new-york"], "includeKeywords": [], "excludeKeywords": [], } # Run the Actor and wait for it to finish run = client.actor("accountable_eel/eventbrite-events-lookup").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 '{ "searches": [ "ny--new-york" ], "includeKeywords": [], "excludeKeywords": [] }' | apify call accountable_eel/eventbrite-events-lookup --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/eventbrite-events-lookup" } } } ``` 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/FUgnQcC0vJObL4mHu/builds/9HEzbjuDbA5Vf4wII/openapi.json