Skip to content

September 23, 2026 · 12 min read

Eventbrite Events Scraper: 1,762 of 1,851 Runs Succeeded (2026)

By Crawlerbros Engineering Team

Each event record carries 29 fields of structured data, including direct checkout links, geocoordinates, and uncropped master cover images. You can test this Actor on Apify's free plan, which covers up to 2,500 results before incurring charges. Browse pages are read directly from live server data without requiring proxies or authentication cookies. This scraper is built for analysts, marketers, and developers who need clean event feeds, and is not for anyone who requires buyer contact details beyond primary organizer IDs.

Try it before you read further. Apify's free plan includes $5.00 of usage every month with no credit card, enough for up to 2,500 results at $0.002 each before platform usage. Open Eventbrite Events Scraper on Apify and run the prefilled example.

How reliable is Eventbrite Events Scraper in production?

Across the last 30 days of public runs on the Apify platform, Eventbrite Events Scraper recorded 1,851 runs with the following outcomes.

Outcome Runs Share
Succeeded 1,762 95.2%
Failed 88 4.8%
Aborted by the user 1 0.1%
Timed out 0 0.0%
Total 1,851 100.0%

Expect about 5 in a hundred runs to fail or time out when scheduling unattended collections. Plan your automated pipelines with built-in retries and failure alerts to handle dropped executions cleanly. Keeping input scopes smaller per run helps prevent unexpected interruptions during high-traffic intervals.

What does it cost to run Eventbrite Events Scraper?

Each result costs $0.002 on Apify's free plan, which is $2.00 per 1,000 results. Starting a run is charged separately at $0.005 per GB of Actor memory. Apify also bills the platform usage each run consumes, at the rates of your Apify plan, on top of these charges.

Apify plan Per result Per 1,000 results
FREE $0.002 $2.00
BRONZE $0.00167 $1.67
SILVER $0.00133 $1.33
GOLD $0.001 $1.00
PLATINUM $0.001 $1.00
DIAMOND $0.001 $1.00

Worked example: collecting 10,000 results costs $20.00 in result charges before run-start fees and platform usage. With 4.8% of runs failing or timing out in the last 30 days, budget for re-running a portion of those batches rather than assuming every run completes.

Controlling the maxItems parameter is the most effective way to manage your spend since result charges apply directly to the number of records written to the dataset. Running a quick test with a low item cap lets you verify data quality before scaling up to larger geographic queries. Because the run-start fee is charged every time execution begins regardless of output, batching your requests efficiently prevents wasted platform credits.

How do you run Eventbrite Events Scraper from the API?

None of its 4 controls is strictly required, so the defaults below produce a valid run on their own. Every value in the payload below comes from the published schema's own prefills, which means you can paste it, swap the token, and get a real result.

Call the synchronous endpoint to start a run and receive dataset items in one request:

curl -X POST "https://api.apify.com/v2/acts/crawlerbros~eventbrite-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"startUrls":["https://www.eventbrite.com/d/united-states/all-events/"],"maxItems":5}'

The same run from Python, using the official client:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run_input = {
  "startUrls": [
    "https://www.eventbrite.com/d/united-states/all-events/"
  ],
  "maxItems": 5
}

run = client.actor("crawlerbros~eventbrite-scraper").call(run_input=run_input)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

And from Node.js:

import { ApifyClient } from 'apify-client'

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' })

const input = {
  "startUrls": [
    "https://www.eventbrite.com/d/united-states/all-events/"
  ],
  "maxItems": 5
}

const run = await client.actor('crawlerbros~eventbrite-scraper').call(input)
const { items } = await client.dataset(run.defaultDatasetId).listItems()
console.log(items)

That endpoint blocks until the run completes. Fine while you are testing a handful of records, risky once a run takes minutes: a dropped connection loses the response even though the run itself finished. Switch to an asynchronous start with polling or a webhook before you schedule anything.

Which Eventbrite Events Scraper inputs matter, and which can you skip?

The input schema provides four optional controls, allowing you to target collection using either direct browse URLs or specific combinations of location and category slugs. Most users should start by setting a single location or category rather than pasting complex custom URLs on their first run. Adjusting maxItems helps you balance data depth against execution speed.

  • startUrls (array): Eventbrite browse URLs (e.g., https://www.eventbrite.com/d/ny--new-york/all-events/). Any filters in the URL are preserved.
  • location (string): City/region slug to use when no startUrls are provided. Format: 'ny--new-york', 'ca--san-francisco', 'united-states', 'online'.
  • category (string): Category slug for the search (e.g., 'music', 'business', 'food-and-drink', 'sports'). Combined with location.
  • maxItems (integer): Maximum number of events to return. Default: 50.

What does Eventbrite Events Scraper return?

Returned records provide structured data such as event titles, start dates, venue addresses, categories, and image galleries that work well for event discovery platforms and market analysis. However, the output conspicuously lacks attendee lists and direct user contact details. Review these fields against your pipeline requirements before committing to large-scale collection.

Identity

  • id: String - Eventbrite event ID
  • summary: String - Short summary (truncated to 1,000 chars)
  • url: String - Event page URL
  • ticketsUrl: String - Direct checkout URL

Dates

  • startDate: String - Start date (YYYY-MM-DD)
  • startTime: String - Start time (HH:MM)
  • endDate: String - End date (YYYY-MM-DD)
  • endTime: String - End time (HH:MM)
  • timezone: String - IANA timezone (e.g., America/New_York)

Venue

  • isOnline: Boolean - Whether it's a virtual event
  • isCancelled: Boolean - Whether the event is cancelled
  • venueName: String - Primary venue name
  • venueAddress: String - Full street address
  • venueCity: String - City
  • venueRegion: String - State / region code
  • venueCountry: String - Country code (US)
  • venuePostalCode: String - ZIP / postal code
  • latitude: Number - Latitude
  • longitude: Number - Longitude

Classification

  • category: String - Eventbrite category (e.g., Music, Business)
  • format: String - Event format (e.g., Concert, Workshop)
  • tags: Array - Organizer tags / keywords
  • language: String - Language code

Other

  • imageUrl: String - Uncropped master cover image URL (typically 2160×1080) - the highest-resolution variant Eventbrite serves
  • gallery: Array - Every variant Eventbrite exposes for the cover image, in descending quality: master (uncropped), large (~1024 px), medium (~640 px), small (~320 px), and the display thumbnail
  • primaryOrganizerId: String - Organizer ID
  • ticketsBy: String - Ticket provider name
  • scrapedAt: String - ISO 8601 scrape timestamp

These are the documented fields. Optional ones can be empty on a given record, so measure how often each field your deliverable depends on is populated across a real sample before automating the handoff.

How do you build the workflow end to end?

Open Eventbrite Events Scraper and work through these in order. Each step ends with something to check, so a bad configuration surfaces on a small run rather than a scheduled one.

  1. Run once with maxItems set to 5 to verify the output shape before spending on large scale extractions.
  2. Set location to a specific slug such as ny--new-york or ca--san-francisco to restrict collection to your target market.
  3. Add category values like music or business to narrow down browse results when pulling broad regional feeds.
  4. Provide specific Eventbrite browse URLs in startUrls when you need exact custom filters preserved in the target request.
  5. Check the returned dataset to ensure startDate and venueName populate correctly for every record.
  6. Scale up maxItems toward 500 once your initial small run successfully writes expected items.

How do you apply it? Three worked playbooks

These are Eventbrite Events Scraper's own documented use cases, each worked through as an operating pattern rather than a description.

Use case 1: Event marketing research

Outcome: Track competitor events in your category / region

Configure: Set location to your target city slug and category to your industry keyword while leaving startUrls empty.

Working method: Pull a small test batch first to verify competitor presence, then expand maxItems to cover the full regional catalog.

Deliverable: A structured dataset of competitor event listings including titles, dates, and ticket URLs.

Stop condition: Zero new competitor listings returned across three consecutive page walks.

Use case 2: Venue analytics

Outcome: Map events by venue to understand utilization

Configure: Target specific venue browse URLs in startUrls or filter by local city slugs with maxItems set to 500.

Working method: Collect all active events for selected venues and aggregate records by venueName to track scheduling density.

Deliverable: A comprehensive inventory of venue event schedules with geocoordinates and category tags.

Stop condition: Venue name fields return null values or venue addresses stop matching target zip codes.

Use case 3: Calendar aggregation

Outcome: Feed event data into calendars or city guides

Configure: Use startUrls with multiple category and location browse pages, capping maxItems at 500 per run.

Working method: Ingest the flat schema output into your calendar pipeline, filtering out cancelled events using isCancelled.

Deliverable: A synchronized feed of upcoming local events ready for calendar import.

Stop condition: Duplicate event IDs flood the dataset or dates fall outside the expected schedule window.

What breaks, and how do you design around it?

  • Over the last 30 days, 4.8% of public runs failed and 0.0% timed out. Build retries and alerting around those rates rather than assuming every run completes.

When pagination reaches your configured maxItems limit, the run terminates automatically. To capture deeper event catalogs, split your geographic targets across multiple smaller runs rather than requesting massive single-batch outputs. Monitor run logs regularly to catch any abrupt pagination halts early.

When should you not use Eventbrite Events Scraper?

Do not use this Actor if your project requires private attendee contact information, deep user profiles, or ticketing data from platforms outside Eventbrite. If you need to aggregate ticketing marketplaces with live pricing data across multiple platforms, use the StubHub Ticket Marketplace Scraper or the Gametime Ticket Marketplace Scraper. For social platform gatherings without traditional ticketing structures, use the Facebook Events Scraper. Similarly, if your objective is tracking open music encyclopedias and global festival lineups rather than commercial ticket sales, the MusicBrainz Events Scraper is a more suitable choice.

What should you check before trusting the output?

  • Check that venueName and venueAddress do not arrive blank for in-person events.
  • Verify that startDate follows the YYYY-MM-DD format and startTime uses HH:MM.
  • Confirm that isOnline correctly reflects boolean values for virtual events.
  • Stop scheduled runs immediately if error rates spike or dataset outputs return empty fields across consecutive pages.
  • Inspect imageUrl to ensure CDN links resolve correctly without truncation.

None of this proves a record is correct. It gives a scheduled Eventbrite Events Scraper run defined points where it should stop instead of quietly passing bad data downstream.

Frequently asked questions

What is the cost per result on Apify's free plan?

Each result costs 0.002 USD, which equals 2.00 USD per 1,000 results. Apify's free plan provides 5.00 USD of monthly platform usage that covers up to 2,500 results of this Actor without requiring a credit card, though run-start fees apply separately.

How reliable is this Actor for scheduled runs?

Telemetry over the last 30 days shows 1,762 successful runs out of 1,851 total runs, with 88 failures and 1 user abort, meaning about 5 in a hundred runs fail or time out. Setting up monitoring for these failures ensures your scheduled pipelines recover smoothly.

Do I need to configure proxies or cookies to scrape Eventbrite?

No proxies, cookies, or logins are required. The Actor extracts embedded server data directly from public browse pages using standard datacenter IPs, making setup straightforward and maintenance minimal.

How are cover images handled in the output data?

The imageUrl field provides the uncropped master cover image at 2160x1080 resolution, representing the highest quality variant available. A gallery array also includes pre-cropped focal-point variants ranging from large and medium sizes down to display thumbnails.

What happens if an event has no physical venue?

Virtual events are flagged with isOnline set to true, and venue fields provide typed default values rather than nulls, ensuring your downstream database ingestion scripts never encounter unexpected null pointer errors.

Where to go next

When you are ready to run it, open Eventbrite Events Scraper on Apify; the free plan covers up to 2,500 results a month.

Start with the Eventbrite Events Scraper Actor page for the current input schema, pricing tier, and run history.

If you are comparing approaches rather than committing to one Actor, these category pages list every option we publish:

Readers running Eventbrite Events Scraper commonly pair it with:

Related guides:

Resources

  • Actor documentation, input schema, and pricing: verified against the published Actor on 2026-09-23.

  • Actor last updated by its maintainers on 2026-04-29.

  • Run outcome figures cover the 30 day public window ending 2026-09-23.

  • Eventbrite Events Scraper on Apify

● Featured actors

Eventbrite Events Scraper

Extract events from Eventbrite like title, date, venue, organizer, ticket price, image, tags. Filter by location, category, or keyword. No proxy required.

Run on Apify ↗