Eventbrite Turbo avatar

Eventbrite Turbo

Pricing

from $4.00 / 1,000 event results

Go to Apify Store
Eventbrite Turbo

Eventbrite Turbo

Eventbrite API alternative for calendars, tourism feeds, and organiser lists. Scrapes public /d/ hubs and /e/ event pages worldwide: ISO times, venue, geo, organiser, and ticket prices. Works worldwide. Same columns as Humanitix Turbo. Pay per event from $4 / 1,000. x402 / Skyfire ready.

Pricing

from $4.00 / 1,000 event results

Rating

5.0

(1)

Developer

Spielraum

Spielraum

Maintained by Community

Actor stats

1

Bookmarked

2

Total users

1

Monthly active users

14 days ago

Last modified

Share

Eventbrite Turbo is a fast, complete Eventbrite event scraper for the Apify platform — a practical Eventbrite API alternative when you need structured rows from public /d/ listings and /e/ event pages. It writes the same professional schema as Humanitix Turbo: ISO times, venue, geo, organiser, and ticket price.

Use it from the Apify Console, via API, or from an agent with x402 / Skyfire. The first 25 events on a Console try-it cost about $0.13 on the Free plan. Apify’s new-account credit (about $5) covers a 1,000-event job at Free-plan rates.

What does Eventbrite Turbo do?

Eventbrite Turbo reads Eventbrite discovery hubs (/d/city/...) and event pages (/e/...). Listing pages are blocked from datacentre IPs, so residential proxy is the default. Each row includes title, times, venue, attendance mode, category, and coordinates when Eventbrite publishes them.

It works worldwide. Melbourne and London are prefilled so you can see AU and UK in one run. There is no Victoria-only or Australia-only skip. rejectOnlineEvents defaults to false.

Output is one row per occurrence, with ISO 8601 timestamps and ISO-2 country codes.

Why use Eventbrite Turbo?

  • Complete event pages — not listing-card stubs. Latitude, longitude, attendance mode, category, and Eventbrite event id are included when present.
  • Predictable costfrom $4.00 / 1,000 results on Gold (Free plan $5.00 / 1,000). No $20/month rental. No extra fee per /d/ page.
  • Guided input — set a city, country, keyword, or date range (this-weekend) when you do not want to hand-build URLs. Start URLs still win if you set them.
  • Agent-ready — pay-per-event, limited permissions, no Standby, so agents can pay with x402 / Skyfire.
  • Same columns as Humanitix Turbo — merge inventories without a second mapper.

Typical uses: local event calendars, tourism and destination feeds, lead generation from organisers, and monitoring competitor programming.

How to scrape Eventbrite events

  1. Open Eventbrite Turbo and click Start.
  2. Keep the Melbourne + London + sample /e/ URLs, or paste your own /d/ and /e/ links.
  3. Or leave Start URLs empty and set Location (London) plus Country (GB).
  4. Cap Max events (default 25) and Max list pages (default 5).
  5. Run and download JSON, CSV, or Excel.
{
"startUrls": [
{ "url": "https://www.eventbrite.com.au/d/australia--melbourne/all-events/" }
],
"maxItems": 25,
"maxListPagesPerStartUrl": 5
}

Input

  • Start URLs/d/ hubs or /e/ events. Wins over helpers when non-empty.
  • Location, city, country, keyword, dateRange — build a discovery URL (today, tomorrow, this-weekend, this-week, this-month).
  • Max events — hard row cap (default 25).
  • Max list pages per start URL — default 5, hard ceiling 50. Keep this modest: residential bandwidth is absorbed into the per-result price.
  • Reject online events — optional; off by default.
  • Proxy — residential Apify Proxy by default. Do not switch to datacentre for /d/ pages unless you know they load.

Output

One row per occurrence. Download JSON, HTML, CSV, or Excel.

{
"source": "Eventbrite",
"sourceEventId": "1996428450237",
"title": "Know Your Rights at Work",
"eventUrl": "https://www.eventbrite.com.au/e/know-your-rights-at-work-tickets-1996428450237",
"startAt": "2026-08-17T17:00:00.000+10:00",
"endAt": "2026-08-17T20:00:00.000+10:00",
"timezone": "Australia/Melbourne",
"venueName": "The Lounge International Students Centre",
"city": "Geelong",
"country": "AU",
"latitude": -38.148,
"longitude": 144.361,
"isOnline": false,
"isFree": true,
"priceDisplay": "Free",
"organiserName": "The Lounge, International Student Centre"
}

Data fields

FieldMeaning
sourceAlways Eventbrite
sourceEventIdEventbrite numeric id
title, eventUrl, ticketUrl, imageUrlIdentity
startAt, endAt, timezoneWhen (ISO 8601)
venueName, streetAddress, city, state, postalCode, countryWhere
latitude, longitudeFrom the event page when published
isOnline, attendanceModeOnline / in-person / mixed
organiserName, organiserUrlOrganiser
currency, priceMin, priceMax, priceDisplay, isFreeTickets
description, category, tagsContent (category is always a shared topic such as Music or Community)
listedFromUrl, extractedAtProvenance

How much does it cost to scrape Eventbrite?

Pay per event only. Store badge from $4.00 / 1,000 (Gold). Free plan $5.00 / 1,000. Actor start stays at Apify’s default $0.00005 per GB. Platform usage is included in the event price — users are not billed compute or proxy on top.

Events (Free plan)Approx. cost
25 (default try-it)$0.13
100$0.50
1,000$5.00

There is no extra charge per listing page. Residential proxy cost is covered by keeping list-page caps low and charging on results. Set maxTotalChargeUsd (default $5) if you want a hard run cap. The minimum max cost per run is $0.05.

Tips

  • If a /d/ page returns 403/405, you are almost certainly off residential proxy.
  • Raise maxListPagesPerStartUrl only after a successful 25-event sample.
  • Combine with Humanitix Turbo for a two-platform calendar.

FAQ

Is this the official Eventbrite API? No. It reads public Eventbrite pages. Respect Eventbrite terms and applicable law.

Why residential proxy? Eventbrite discovery pages are blocked from typical datacentre IPs. Event pages may still load; listings usually will not.

Can agents pay with x402 / Skyfire? Yes. Limited permissions and no Standby, so agents can pay with x402 or Skyfire.

How do I report a bad parse? Use the actor Issues tab.

This actor extracts publicly visible event information. You are responsible for lawful use of the dataset.