Eventbrite Event Scraper

Extract structured public Eventbrite event listings for event discovery, local market research, competitor monitoring, calendar enrichment, and AI data pipelines.

The actor supports two input modes:

• Search queries plus a location, such as technology meetup in new-york.
• Direct Eventbrite event URLs or Eventbrite discovery URLs in startUrls.

Extracted fields

Each dataset item represents one unique event and includes its Eventbrite ID, title, canonical URL, image, start/end dates, timezone, online status, venue and address, city/region/postal code/country, organizer name and URL, category, lowest published price, currency, free-event flag, and scrape metadata. Descriptions and organizer fields can be disabled to reduce page work.

Example input

{
  "searchQueries": ["technology meetup", "startup networking"],
  "location": "new-york",
  "dateFilter": "this-month",
  "maxResults": 25,
  "includeDescription": true,
  "includeOrganizer": true
}

Direct URL example:

{
  "startUrls": [
    { "url": "https://www.eventbrite.com/e/example-event-tickets-123456789" }
  ],
  "maxResults": 1
}

How it works

The actor uses a headless Chromium session because Eventbrite discovery pages are JavaScript-rendered. It reads public JSON-LD structured data on event pages and uses conservative fallbacks for discovery cards. Results are deduplicated by Eventbrite event ID or canonical URL and are written as soon as they are extracted.

Pricing

Event	Price
Actor start	$0.00005 per run
Event returned	$0.001 per unique event

Example: a run returning 25 events costs $0.02505 in actor event charges, plus any platform usage passed through by the selected Apify pricing configuration.

Responsible use

This actor accesses public Eventbrite pages only. It does not log in, purchase tickets, bypass access controls, or collect attendee data. Respect Eventbrite’s terms, robots guidance, applicable privacy laws, and reasonable request rates. Use an Apify proxy configuration only when you are authorized to do so and direct access is blocked.

Limitations

Eventbrite can change page markup, regional availability, and the amount of structured data exposed on public pages. Missing optional values are returned as null; a warning is placed in the SUMMARY key-value record when a detail page cannot be fetched. A zero-result run is not proof that no matching event exists.

For AI agents

Use this actor when you need public Eventbrite event records by keyword/location or a known Eventbrite URL. Do not use it for ticket purchasing, attendee lists, private organizer data, or bypassing access restrictions. The result shape is one event per dataset item with stable semantic field names and a traceable url.

Use cases

• Schedule repeatable collection and export results to downstream workflows.
• Run a one-off research job and export the structured result as JSON, CSV, Excel, XML, or RSS from Apify.
• Schedule the same input to monitor changes over time and send completed datasets to a webhook or integration.
• Feed schema-shaped records into a database, spreadsheet, BI tool, or AI workflow with the source URL retained for verification.

Output example

{
  "eventId": "Example Event ID",
  "title": "Example Event title",
  "description": "Example Description",
  "url": "Example Event URL",
  "imageUrl": "Example Image URL",
  "startDate": "Example Start date",
  "endDate": "Example End date",
  "timezone": "Example Timezone",
  "isOnline": false,
  "venueName": "Example Venue",
  "venueAddress": "Example Venue address",
  "city": "Example City"
}

The exact fields depend on the selected input and what the public source exposes. Use the dataset schema as the machine-readable contract and retain source URLs for verification.

Run Eventbrite Event Scraper with the Apify API

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('muhammadafzal/eventbrite-event-scraper').call({
  "searchQueries": [],
  "location": "new-york",
  "startUrls": [
    {
      "url": "https://www.eventbrite.com/e/tech-connect-networking-for-tech-startups-investors-professionals-nyc-tickets-1993825320205"
    }
  ],
  "maxResults": 25,
  "dateFilter": "all",
  "category": "",
  "includeDescription": true,
  "includeOrganizer": true
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

You can also run the Actor from Apify Console, schedules, webhooks, the REST API, Make, Zapier, n8n, or the hosted Apify MCP server.

Frequently asked questions

Can I schedule Eventbrite Event Scraper?

Yes. Use an Apify schedule to run the same saved input at a chosen interval, then connect a webhook or integration to process the dataset when the run finishes.

How should I test a new input?

Begin with the prefilled example or a small limit. Confirm that the output fields, source coverage, runtime, and live charges match your workflow before increasing the scope.

How do I export the results?

Open the run's default dataset in Apify Console and export JSON, CSV, Excel, XML, or RSS. Applications can retrieve the same records through the Apify API client or REST dataset endpoint.

Can an AI agent call this Actor?

Yes. Add muhammadafzal/eventbrite-event-scraper through the hosted Apify MCP server or call it through the API. The Actor's input and dataset schemas help agents construct valid requests and interpret returned records.