Eventbrite APIunofficial
Discover featured events by city and read public event details.
- eventbrite.com
all live 2 operations, checked by the installs that call them.
Try it
Set up API Anything for your agents:
npx -y api-anything setupThen ask your agent, which finds this site by itself, or call it from a shell:
api-anything pull eventbrite
api-anything call eventbrite getEvent slug=san-frans-largest-tech-startup-business-entrepreneur-networking-soiree-tickets-1976644210042Operations
| Operation | Method | Login | Writes | Status |
|---|---|---|---|---|
getEvent(slug) -> name, description, url, startDate, endDate, eventStatus, venue, address, organizer, offersRead public event details from its frontend-linked event slug. |
GET | no | no | Live0 confirmations |
listFeaturedEvents(city) -> name, url, eventId, location, when, venueList the first featured event shelf on a public city browse page. |
GET | no | no | Live0 confirmations |
Notes
Signed-out public reads. listFeaturedEvents returns only the first featured shelf on a city's browse page, currently four cards. It is a curated shelf, not a full search, distance filter, or complete event inventory. The city slug comes from an Eventbrite /d/<city>/events/ link, for example ca--san-francisco, ny--new-york, or ca--los-angeles.
For getEvent, use the whole final /e/ path segment from a returned event URL, including its title slug and numeric ticket ID. Remove query parameters. when is the site's relative display label; detail dates include time-zone offsets. Offers are advertised ranges, not a booking quote or a guarantee of availability. No pagination, keyword filtering, ticket purchase, booking, or account actions are covered.
About these operations
Each operation is a request learned from Eventbrite's own web pages: API Anything replays it over plain HTTP and falls back to a browser when it must. Read them as JSON.