Submit an Eventbrite event - the full URL or just its numeric id, both work - and get the listing back as a row: what it is called, when it starts and ends, where it is, who is running it and what it costs. Ten columns, and a few honest notes about which of them you can rely on.
Two of our runs submitted the full https://www.eventbrite.com/e/1417752679429 and one submitted the bare id 1417752679429. Both returned the same event. So you do not have to reconstruct URLs from an id column you already hold.
The same event came back with start of 2026-07-04T21:00:00-04:00 on 30 June and 2026-07-11T21:00:00-04:00 a fortnight later. Nothing changed but the date. If you are building a calendar, re-scrape rather than assuming the first answer holds.
On the same event, two runs returned both fields empty and one returned 0.0 and USD. Write the importer to accept blanks. And note that price arrives as a string, not a number - "0.0", quotes and all.
One of our four runs returned no rows and no columns at all - not an empty row, an empty result. Reconcile the export against your input list rather than assuming every submitted event produced a row.
Verbatim from the export: 447 Edgewood Avenue Southeast, Atlanta, GA 30312, Atlanta, GA, US. City and state appear twice, once inside the street portion and once after it. Parse from the right, or split on commas and dedupe, before you geocode.
venue is where it happens and organizer is who is running it, and they are genuinely different values - a bar in one column, a promoter in the other. That split is what makes the export useful for outreach rather than just for listings.
Read from the header of a real export of this service, in sheet order.
2026-07-11T21:00:00-04:00. Parse the offset; do not assume UTC.start, crossing midnight.price, and empty whenever price is. Read it rather than assuming USD.Ten columns per row · CSV, JSON or Excel
Four runs sit behind this page and three returned data - all three for the same event, so this describes the schema and how the fields behave, not Eventbrite's catalogue. We make no claim about how many events exist, what they typically cost, or how often price is filled: one event is not a sample, and saying otherwise would be inventing a measurement.
The organizer column is the one that turns a listing into a contact. Collect it across the events in your category, count who appears repeatedly, and you have a shortlist of the people worth talking to.
venue and address together tell you where the activity is. Group by venue and count events to find the rooms a scene really runs through, rather than the ones with the best marketing.
start and end arrive parseable with a real UTC offset, so a nightly re-run keeps a calendar honest. Re-run rather than cache: we watched the same event move a week between scrapes.
Take the organizer and venue columns into the Email & Contact Scraper and the event list becomes a list you can actually reach.
One-time, on signup. No card, and nothing to cancel afterwards.
Billed on rows actually returned. A run that comes back empty - and one of our four did - is not a row of event data, and is not charged as one.
Credits do not expire on a monthly cycle. Run a batch before a season and nothing again until the next one.
LIVESCRAPER10 at checkout.Events from the Google results page rather than from one platform - useful for finding what Eventbrite does not list.
Turn the venue column into full business records - phone, website and rating for the rooms your events run in.
Feed organisers and venues in and get contact details out, so an event list becomes a reachable one.
Find the event pages in the first place, then bring the URLs back here for the structured detail.
A public event page is an advertisement - it exists to be read. The caveats are about the organiser, not the event.
An event listing is published so that people find it. Its name, time, venue, address and price are facts about something happening in public, and reading them from a page anyone can open is the same act a prospective attendee performs. Nothing in these ten columns describes an attendee: there is no ticket buyer, no email, no phone number and no account.
One column deserves care. organizer is often a company, but on smaller events it is a person's own name, and a name attached to a contactable role is personal data in the GDPR sense even when it was published voluntarily. If you are building an outreach list from it, that is a legitimate-interests processing decision with the usual obligations - tell people where you got their details, and honour an opt-out. This is not a reason to avoid the column; it is a reason to handle it as what it is.
Our own terms are the same as on every other service here. Publicly available pages only, nothing behind a login, no third-party trackers on the data layer, and exports auto-delete after 30 days. Your first 500 rows are free and need no credit card.
query, name, start, end, venue, address, price, currency, organizer and url. One row per event.https://www.eventbrite.com/e/1417752679429 and one submitted the bare id 1417752679429, and both returned the event. If you already hold ids, you can use them directly.2026-07-04T21:00:00-04:00 and then 2026-07-11T21:00:00-04:00 - same event, next date. If you keep a calendar, re-scrape rather than caching the first answer.0.0 and USD. Write the importer to accept blanks, and note that price is a string rather than a number.2026-07-11T21:00:00-04:00. Parse the offset; do not assume the timestamp is UTC.447 Edgewood Avenue Southeast, Atlanta, GA 30312, Atlanta, GA, US - the city and state appear inside the street portion and again after it. Split on commas and dedupe before geocoding.Ten columns per event, from a URL or a bare id. Your first 500 rows are free, then $0.002 each.
The Eventbrite Scraper takes an event and returns it as a row of ten columns: query, name, start, end, venue, address, price, currency, organizer and url. You can submit either the full event URL or the bare numeric id - both appeared in our runs and both worked, which matters if you already hold ids in a database and would otherwise have to rebuild URLs from them.
Four behaviours are worth knowing before you build on it, all observed rather than assumed. Times come back as ISO 8601 with a UTC offset rather than a trailing Z, so parse the offset instead of treating the value as UTC. Recurring events return their next occurrence: we scraped one event on 30 June and again a fortnight later and the start moved from 4 July to 11 July with nothing else changed, so a calendar built on a cached first answer will drift. price and currency are optional in practice - on that same event, two of three populated runs returned both empty and one returned 0.0 and USD - and price is a string rather than a number. And a run can return nothing at all: one of our four came back with no rows and no columns, which is why you reconcile against the input list rather than assuming a row per submission.
The address is worth one more line. It arrives as a single string that repeats the city and state, verbatim 447 Edgewood Avenue Southeast, Atlanta, GA 30312, Atlanta, GA, US, so split on commas and dedupe before geocoding. venue and organizer are separate columns holding genuinely different values - the room and the promoter - and that split is what makes the export useful for partnership work rather than just for listings.
We are being deliberately careful about what this page does not say. All three populated runs behind it are the same event, so there is nothing here about how many events Eventbrite carries, what they typically cost, which categories are covered, or how often any field is populated across the platform. One event is not a sample, and quoting a rate from it would be inventing a measurement. On the legal side, an event listing is published to be found and none of the ten columns describes an attendee - but organizer is sometimes a person's own name, which is personal data even when published voluntarily, so treat an outreach list built from it accordingly. Publicly available pages only, no third-party trackers on the data layer, and exports auto-delete after 30 days. Your first 500 rows are free and need no credit card.