Eventbrite Scraper: Events by Query and Location

Eventbrite Events: Search by Query and Location

Search Eventbrite public listings by query and location. One row per event with title, start and end, venue, city, online flag and URL. Organizer names and ticket prices are not on Eventbrite's search pages; the Eventbrite Event Data Scraper reads them from each event's own page.

How to use

Provide one or more search queries (kebab-case, matching Eventbrite's URL format) and an optional location slug.

Input shape

{
  "queries": ["tech-conference", "design-workshop", "startup-pitch"],
  "location": "united-states",
  "maxEventsPerQuery": 50
}

Field	Type	Default	Description
queries	array of strings	["tech-conference","design-workshop","startup-pitch"]	Search terms in kebab-case
location	string	"united-states"	Eventbrite location slug (e.g. "new-york", "london-gb")
maxEventsPerQuery	integer	50	Maximum events returned per query (cap per query, not total)

Queries map to the Eventbrite search URL pattern https://www.eventbrite.com/d/{location}/{query}/. Up to 3 pages of results are fetched per query.

Example output row

{
  "query": "design-workshop",
  "id": "987654321",
  "title": "Product Design Summit 2025",
  "organizer": null,
  "startDate": "2025-09-12T09:00:00",
  "endDate": "2025-09-12T18:00:00",
  "isOnline": false,
  "venueName": "San Francisco Convention Center",
  "city": "San Francisco",
  "priceMin": null,
  "priceMax": null,
  "url": "https://www.eventbrite.com/e/product-design-summit-2025-tickets-987654321"
}

Pricing

Pay per event. Price per 1,000 events:

Event	Base price	Bronze	Silver	Gold
Eventbrite event extracted	$0.30	$0.27	$0.24	$0.21

Bronze, Silver and Gold are the discounts Apify gives users of its paid plans. The Pricing tab always shows the current prices.

You are charged only for rows actually delivered to the dataset. A query that returns zero results costs nothing.

Buyer

• Event marketers mapping competitor and co-marketing opportunities by scanning upcoming conferences and workshops in their niche.
• Sales teams finding sponsorship and speaking slots: upcoming events by topic, city and date.
• Market researchers tracking how often events on a topic run, where, and whether in person or online.
• Event organizers checking the dates and venues of similar events in the same city before setting their own.
• Developer relations and community teams finding meetups and hackathons to join or sponsor.

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/eventbrite-events-search").call(run_input={"queries": ["tech-conference", "design-workshop", "startup-pitch"], "maxEventsPerQuery": 20})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/eventbrite-events-search').call({"queries": ["tech-conference", "design-workshop", "startup-pitch"], "maxEventsPerQuery": 20});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~eventbrite-events-search/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"queries": ["tech-conference", "design-workshop", "startup-pitch"], "maxEventsPerQuery": 20}'

Output fields, real sample rows, the price and this code for Python, JavaScript and cURL are also in the guide to this actor.

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/eventbrite-events-search",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

FAQ

Do I need an account, cookies or an API key?

No. The actor reads public data without logging in. You only need an Apify account to start it.

How many results can one run return?

Set maxEventsPerQuery to the number you need. Large jobs can also be split into several runs or scheduled.

How am I charged?

Pay per event, at the prices on the Pricing tab for your Apify plan (the Pricing section of this page lists them). The platform usage of the run is included in those prices, and your spending limit for a run is always respected.

Why did my run return no results?

The status message and the log of the run say why: usually nothing matched the input, or the source did not answer for a moment. Check the input against the example above and run it again.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

Is collecting this data allowed?

The actor collects data that the source publishes openly, without a login. Public data can still be personal data under laws such as the GDPR, and sources have their own terms: make sure your use of the data follows the rules that apply to you.

What happens when the source changes?

An automated test runs the actor every day on the example input and checks the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.

Related actors

• Eventbrite Event Data Scraper: City, Dates, Ticket Prices
• Luma Event Scraper

Source

Data is scraped from Eventbrite's public search pages at:

https://www.eventbrite.com/d/{location}/{query}/

The actor reads the window.__SERVER_DATA__ JSON blob embedded in the HTML by Eventbrite's server-side renderer. When that blob is absent, it falls back to <script type="application/ld+json"> Schema.org Event nodes emitted for SEO. No private API or authentication is used. Only publicly visible event listings are returned.