What is on, where, and when
The Eventbrite API returns live event data as clean JSON.
5 active endpoints. Every call is 1 credit.
- POST/eventbrite/v1/search
- POST/eventbrite/v1/detail
- POST/eventbrite/v1/organizer
- POST/eventbrite/v1/organizer_events
- POST/eventbrite/v1/browse
What Eventbrite endpoints does ReefAPI ship?
5 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Eventbrite API
3 of 5 endpoints, ready to run
Events matching a query and a place, with the name, dates, image and link on every row.
{ "ok": true, "meta": { "api": "eventbrite", "endpoint": "search", "mode": "live", "latency_ms": 2463.2, "record_count": 20, "cache_hit": false }, "data": { "events": [ { "event_id": "1987408189394", "name": "Trends in Defence Tech", "url": "https://www.eventbrite.co.uk/e/trends-in-defence-tech-tickets-1987408189394", "start_date": "2026-09-09", "end_date": "2026-09-09", "image": "https://img.evbuc.com/https%3A%2F%2Fcdn.evbuc.com%2Fimages%2F1182160588%2F3000991917%2F1%2Foriginal.20260414-182319?crop=focalpoint&fit=crop&w=300&auto=format%2Ccompress&q=75&sharp=10&fp-x=0.5&fp-y=0.5&s=90b7f93a088694255af3fc046ac2cbd6", "is_online": false, "venue": { "name": "Bird & Bird", "street": "12 New Fetter Lane", "city": "London", "region": "England", "postal_code": "EC4A 1JP", "country": "GB", "latitude": 51.516133, "longitude": -0.108974 } }, { "event_id": "1997248313470", "name": "Jollof & Tech- V1", "url": "https://www.eventbrite.co.uk/e/jollof-tech-v1-tickets-1997248313470", "start_date": "2026-09-05", "end_date": "2026-09-05", "image": "https://img.evbuc.com/https%3A%2F%2Fcdn.evbuc.com%2Fimages%2F1190692791%2F3010280185921%2F1%2Foriginal.20260810-095839?crop=focalpoint&fit=crop&w=267&auto=format%2Ccompress&q=75&sharp=10&fp-x=0.506&fp-y=0.148&s=6796d32ac1f2248ce1b0026a951628c2", "is_online": false, "venue": { "name": "SE18 6NE", "street": "Hare Street", "city": "London", "region": "England", "postal_code": "SE18 6NE", "country": "GB", "latitude": 51.492885, "longitude": 0.063538 } }, { "event_id": "1992358088676", "name": "Climate Tech Time", "url": "https://www.eventbrite.co.uk/e/climate-tech-time-tickets-1992358088676", "start_date": "2026-09-23", "end_date": "2026-09-23", "image": "https://img.evbuc.com/https%3A%2F%2Fcdn.evbuc.com%2Fimages%2F1187559075%2F163485174131%2F1%2Foriginal.20260624-132652?crop=focalpoint&fit=crop&w=267&auto=format%2Ccompress&q=75&sharp=10&fp-x=0.945&fp-y=0.506&s=a662f96ae27ba8c83cbf546d07c7d685", "is_online": false, "venue": { "name": "The Conduit", "street": "6 Langley Street", "city": "London", "region": "England", "postal_code": "WC2H 9JA", "country": "GB", "latitude": 51.513219, "longitude": -0.125078 } } ] } }
How the Eventbrite API works
Eventbrite is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 184 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Finding who runs the events in a niche
One event is a listing. The organiser behind it, running a series every month, is the actual thing worth knowing about — for partnerships, for research, or for a calendar.
{"query": "tech", "location": "london", "date": "this-weekend"}Location plus a date window is the query shape people actually have. Rows carry the dates and the link.
{"organizer_id": "…"}Then the organiser behind the interesting one, and their whole programme.
Going from event to organiser to their full series is the step that turns a listings feed into a picture of who is active in a scene.
curl -X POST https://api.reefapi.com/eventbrite/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"music","location":"united-states--new-york"}'{
"ok": true,
"data": { … },
"meta": {
"api": "eventbrite",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What a discovery result carries, and what the fields really mean
Search and browse both return the same event shape. The fields below are measured from live Berlin and London queries — read the notes on dates and URLs before you build on them.
| Field | Measured example | What to know |
|---|---|---|
| event_id | "1982123791618" | 13 digits, returned as a string. It is also the last path segment of the event URL. |
| start_date / end_date | "2026-08-29" / "2026-08-30" | date only, no time and no timezone. A two-day span means a multi-day event, not an all-day one. |
| url | eventbrite.de · eventbrite.ca | the event's own Eventbrite domain, which does NOT track the venue country — see the FAQ |
| is_online | false | online events return no meaningful venue geography |
| venue | {name, street, city, region, postal_code, country, latitude, longitude} | region is the local subdivision code — measured "BE" for Berlin — not a country code |
| image | img.evbuc.com/... ?w=512 | a proxied thumbnail with sizing parameters already applied |
| meta.pagination | {page, has_more, next_page} | search returned 20 events per page; browse returned 8 for a category query |
| free | boolean filter | narrows to free events; a measured free search still returned a full page of 20 |
search takes query, location, category, date, free and page and is the keyword surface; browse takes only location and category and is the directory surface. A measured Berlin music browse returned 8 events while a plain Berlin search returned 20, so they are different indexes rather than the same one filtered — check both when you are trying to be exhaustive about a city.
How the search is addressed, and what a row carries
Measured on city searches.
Events are inherently local and the search is built around that. A query without a place returns a global mixture that is rarely what anyone wants, so pass the location.
This-weekend and similar windows are accepted directly, which matches how people ask the question and removes the date arithmetic from the caller.
Free events are a distinct category of thing — community meetups, launches, open days — and filtering for them upstream separates them from the paid conference listings that otherwise dominate.
Start and end dates, the event name, the image and the ticket link are all on the search row, so a listings view needs no per-event call.
This platform is strong for professional and community events in English-speaking cities and thinner elsewhere and for other kinds of gathering. It is a large slice of the events world rather than all of it.
What people build with Eventbrite
The jobs this data is most often used for.
endpoints
credit per call
Event and local-discovery apps call search to list upcoming events by city and date.
Marketing tools use organizer_events to track a competitor's or partner's event calendar.
Aggregators use detail and venue to enrich an event with time, place and ticket info.
What Eventbrite data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
Full pricing →- 1,000 free credits on signup, no card
- One key, all 184 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/eventbrite/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"music","location":"united-states--new-york"}'import requests
r = requests.post(
"https://api.reefapi.com/eventbrite/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"query": "music",
"location": "united-states--new-york"
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Eventbrite.
Get a free key →Why do two events in the same city have different Eventbrite domains?▾
Because the domain follows the organizer's account, not the venue. Two measured events both physically in Berlin came back with one URL on eventbrite.de and another on eventbrite.ca — the second is a Canadian organizer running a German date. Never infer the country from the URL. venue.country is the field that actually answers that, and it returned "DE" for both.
Do the dates include a start time?▾
No. start_date and end_date on a discovery result are calendar dates — measured "2026-08-29" and "2026-08-30" — with no clock time and no timezone attached. That is enough to answer 'what is on this weekend' and not enough to build a calendar invite. Treat an end_date later than the start_date as a genuinely multi-day event; it is not a placeholder for an all-day flag.
What is the region field on a venue?▾
The local subdivision code, not a country. Measured Berlin venues returned region "BE" alongside country "DE" — that is the German state of Berlin, and it collides visually with the ISO country code for Belgium. If you are mapping regions, key on the country plus region pair, never on region alone. postal_code, street, latitude and longitude come back on the same object and are the reliable way to place an event precisely.
How do I find only free events?▾
Pass free on search. Worth knowing what that does and does not tell you: a measured free search on Berlin still returned a full page of 20 events, so a free filter is not a niche query in a large city. The discovery result itself carries no price field, so free is a filter you apply rather than a value you read back — if you need to display a price, that is not something the search surface gives you.
How many events come back, and how do I get the rest?▾
A measured search returned 20 events per page with meta.pagination reporting page, has_more and next_page; browse returned 8 on a category query. Follow next_page rather than computing offsets. meta.stop_reason tells you why a page ended — "limit_reached" means you hit the page size, not the end of the inventory, so has_more is the field that decides whether to keep going.
Can I search by keyword and city together?▾
Yes, and that is the normal use: query plus location, optionally narrowed with category, date and free. A measured London search for "startup" returned a full page of 20. location is free text resolved to an Eventbrite place, so a city name works and a more specific string sharpens it. Omit query entirely and you get the city's general listings, which is the cheap way to size a market before filtering.
Is an online event's venue meaningful?▾
No — check is_online first. When it is true the geography on the record does not describe where anyone will physically be, so filtering a city query by distance will quietly mix in events that have no location at all. It is the one boolean worth branching on before you use any of the venue fields, and it is present on every discovery result.
What is the Eventbrite API?▾
Eventbrite API is a ReefAPI endpoint group for eventbrite It returns live JSON through POST requests under /eventbrite/v1.
Is the Eventbrite API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Eventbrite calls use the same shared credit balance as every other ReefAPI engine.
Do I need an Eventbrite login or account?▾
No login to Eventbrite is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Eventbrite data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Eventbrite API use?▾
Eventbrite actions currently cost 1 credit per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.
Can I call Eventbrite from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call eventbrite actions with the same key, credit pool and JSON envelope used by normal REST requests.
Is the Eventbrite API an Eventbrite scraper?▾
It is the managed alternative to a DIY Eventbrite scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same eventbrite back as clean JSON.
25 Media, Film & Knowledge APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Eventbrite, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 183 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-08-30.