Eventbrite Events Scraper

Export public Eventbrite events from discovery URLs or a list of event links. Eventbrite Events Scraper returns event URLs, dates, venues, organizer names and available ticket-price information for event research and organizer analysis.

Discovery URLs are interpreted as search terms, not as exact copies of Eventbrite's page filters. Results and optional fields depend on what Eventbrite makes available. No login or Eventbrite API token is required.

Quick start

1. Open the Actor's Input tab and paste a public Eventbrite discovery URL or direct event URL.
2. Start with a small limit, such as the input below.
3. Run the Actor, then export the dataset as CSV, Excel or JSON. Check itemType before using rows as events.

{
  "startUrls": [{ "url": "https://www.eventbrite.com/d/online/events/" }],
  "maxItems": 20,
  "maxPages": 2,
  "includeEventDetails": true,
  "dedupeEvents": true
}

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.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Export Eventbrite music events summary
• Export Eventbrite business events in London
• Export Eventbrite tech events in NYC

What you get

Saved public event rows can include titles, dates, venue or online information, organizer names and ticket-price signals. The dataset can also contain separate diagnostic rows, so filter itemType before using it as an event list. Optional fields and successful detail enrichment are not guaranteed.

Who is it for?

• Event researchers preparing a public event sample for manual review.
• Editorial teams checking source links and dates before publishing event roundups.
• Venue and market analysts comparing available public venue or organizer information.
• Data teams organizing a curated list of known event URLs.

How you can use the data

• Review a current online-event sample. Use the existing online-discovery URL with small event and page caps. Keep only event rows, then inspect title, eventUrl, startDate, timezone and isOnline before using them in a calendar.
• Build a curated known-event sheet. Supply direct public event URLs with details enabled. Retain available dates, venue, organizer and ticket-price fields, and open the source links to check current details before sharing them.
• Research discovery topics without assuming exact filters. Use the existing business, music or tech examples as search seeds. Discovery paths become search terms rather than faithful copies of location, category, date or sort controls.
• Separate outcomes from event records. Exclude itemType: error rows from an event export and inspect their diagnostic codes separately. A failed input can coexist with useful records from another input, and an empty discovery response needs its recorded explanation.

Input settings

Setting	JSON key	Purpose
Eventbrite URLs	startUrls	Required list of public discovery or direct event URLs. The form prefills an online-events URL.
Maximum events	maxItems	Bound saved event rows across the run. Form default 20.
Maximum search pages	maxPages	Bound discovery requests per URL. Form default 3.
Fetch event details	includeEventDetails	Request richer event information. Default true.
Dedupe events	dedupeEvents	Skip repeated event IDs/URLs across inputs. Default true.

See input-field help for omitted API values and discovery limitations. A direct event URL with details disabled may produce only an ID and URL. Enable details for useful curated-event results.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

The dataset contains itemType: "event" records and may contain itemType: "error" diagnostic records. Filter by itemType when exporting event-only data. Optional fields can be absent. An unavailable detail lookup can leave only the listing information.

Illustrative shape only (not a measured event):

{
  "itemType": "event",
  "eventId": "123456789012",
  "eventUrl": "https://www.eventbrite.com/e/example-tickets-123456789012",
  "title": "Example event",
  "isOnline": true,
  "isFree": true,
  "priceText": "Free",
  "sourceUrl": "https://www.eventbrite.com/d/online/events/",
  "scrapedAt": "2026-10-24T00:00:00.000Z"
}

Fields	Meaning
itemType	event or error.
eventId, eventUrl, title	Event identifier, link and available title.
descriptionText	Available description or summary, not guaranteed full text.
startDate, endDate, rawDateText, timezone	Available dates and timezone. Date strings may be UTC or local.
isOnline, venueName, venueAddress	Online flag and available venue information.
city, region, country, latitude, longitude	Available location data.
organizerName, organizerUrl	Available public organizer information.
category, tags	Available labels. Category coverage is limited.
priceText, minPrice, currency, isFree	Available ticket-price signals, not a live ticket inventory or checkout quote.
imageUrl, status	Available event image and status.
sourceUrl, scrapedAt	Input URL and extraction timestamp.
errorCode, errorMessage	Diagnostic reason on an error record.

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 for the available formats and field options.

Pricing

Pay-per-event pricing uses a start event once when a run starts and a result event for each saved event row. Diagnostic rows are not charged as event results.

See the live Pricing tab for current rates and discounts.

Tips for best results

• Set both event and page caps. Diagnostic rows can appear in addition to the saved-event limit.
• Enable details for curated event URLs. With details off, a direct URL can produce only its ID and link.
• Filter row types before calendar or spreadsheet use. Keep event records separate from input-failure and no-event diagnostics.
• Verify dates and timezones at source. Returned date strings can be UTC or local, and optional venue or organizer fields can be missing.
• Treat ticket prices as observations. Recheck the public event page rather than using a saved price signal as a live booking quote.

Limits and caveats

Discovery paths become search terms. Query parameters, exact location or category filters and page sorting are not reproduced. Online discovery paths request online events, and there is no user-selectable sort order or guarantee of every event in a city or topic.

Only public event information is supported, without login or an Eventbrite API token. Attendee lists, organizer contact emails, orders and private account data are not returned. Site restrictions or changes can prevent extraction.

A failed source can produce an INPUT_FAILED diagnostic while other inputs continue. An empty discovery response currently produces NO_EVENTS_FOUND. Invalid URLs are skipped, and a run with no valid URLs fails. Diagnostic rows are additional to the event cap and do not produce event-result charges.

Dates, organizers, descriptions and prices can be absent. Unavailable detail lookups can leave listing information only. Boolean flags do not independently prove availability or a current ticket price, and ticket-price fields are not a live inventory or checkout quote.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. 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 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 for your chosen tool.

For a custom connection, an Apify webhook 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, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~eventbrite-events-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "startUrls": [
    {
      "url": "https://www.eventbrite.com/d/online/events/"
    }
  ],
  "maxItems": 20,
  "maxPages": 2,
  "includeEventDetails": true,
  "dedupeEvents": true
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/eventbrite-events-scraper').call({
  "startUrls": [
    {
      "url": "https://www.eventbrite.com/d/online/events/"
    }
  ],
  "maxItems": 20,
  "maxPages": 2,
  "includeEventDetails": true,
  "dedupeEvents": true
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/eventbrite-events-scraper').call(run_input={'startUrls': [{'url': 'https://www.eventbrite.com/d/online/events/'}], 'maxItems': 20, 'maxPages': 2, 'includeEventDetails': True, 'dedupeEvents': True})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API usage notes

The REST request returns run metadata. After it finishes, retrieve items using the returned defaultDatasetId.

MCP and AI agents

You can ask your AI assistant to collect data with Eventbrite 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. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin 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 and ask it to find Fetch Cat's Eventbrite 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.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. 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:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/eventbrite-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 Eventbrite Events Scraper by Fetch Cat, or give it the identifier fetch_cat/eventbrite-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 Eventbrite Events Scraper to collect up to 5 public online events from https://www.eventbrite.com/d/online/events/ with at most 1 discovery page. Show event links, dates and timezones, excluding diagnostic rows from the event table.”
• “Retrieve details for the 3 public Eventbrite event URLs I provide. Show available venue, organizer and price information with source links so I can verify them before creating a calendar entry.”
• “Collect up to 5 events from the public tech-discovery URL I supply, with at most 1 discovery page. Keep source URLs and explain any input or no-event diagnostics without assuming the URL's exact filters were reproduced.”

Normal Apify charges apply. Check the live Pricing tab 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. This experimental option lets an agent use Apify without a conventional account.

Apify AGI 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 to choose the right setup.

FAQ

Is this an Eventbrite API alternative?

It provides public event data through Apify's API. It is not the official Eventbrite API and does not grant access to private event-management data.

Can I export Eventbrite events to CSV or Excel?

Yes. Export the default dataset in Apify, filtering out diagnostic rows if you want events only.

Does it support “events near me” or “events today”?

Supply a relevant discovery URL, but expect a search seed rather than exact browser location or date filters. Inspect results for your intended area and dates.

Why are results missing or incomplete?

The source may return no events, restrict access or omit details. Review diagnostic rows and the run log. A completed run alone does not guarantee useful event records.

Does one unavailable event stop the batch?

A failed detail lookup can retain a listing-only record. A failed discovery source produces a diagnostic row while later sources continue. Invalid or entirely missing input can still fail the run.

Related Actors

• Meetup Events Scraper — Research events on another platform.
• Website Content Crawler Lite — Collect text from public websites for further analysis.
• Website Contact Finder — Find public contacts on websites you supply separately.
• Google Maps Places Scraper — Research venues and local businesses.
• Google Maps Reviews Scraper — Collect public place reviews for venue research.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue 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. 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 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. ♥