canonical: https://jentic.com/apis/Eventbrite/eventbrite

# Eventbrite API

The Eventbrite API searches public events by location, date, category, and keyword and returns full event details including venue, organizer, and ticket status. It exposes an OAuth 2.0 bearer-authenticated search operation with latitude, longitude, radius, price, and start-date filters, an operation for retrieving a single event by its id, and a category listing used to refine searches. It reads live event data and is suited to discovery, aggregation, and alerting rather than ticket sales.

## For AI agents

Search Eventbrite for public events by location, date, category, and price, and retrieve full event details including venue, organizer, and ticket status. Returns structured event data for discovery, aggregation, and alerting.

## Scope

Does not handle ticket purchases, event creation, attendee management, or payments. Use for public event search and discovery only.

## Capabilities

- Search public events by location, date, and keyword using latitude, longitude, and a search radius
- Retrieve full event details including venue, organizer, and ticket status by event id
- Browse the Eventbrite category taxonomy to refine event searches
- Filter event searches by price, format, and start-date range
- Sort event search results by date, distance, or best match

## Use cases

### AI Agent Event Discovery

An AI travel or concierge agent connected through Jentic searches Eventbrite for events matching a user's city, date window, and interests, then returns venue, timing, and ticket status. The agent calls the event search operation with location and start-date filters and expands individual events for full details, so a planning assistant can assemble an itinerary without a human browsing the site.

Example prompt: Search Eventbrite for music events within 20 miles of Austin between two dates, then retrieve full details for the top three results

### Local Event Aggregation

A city guide or listings site pulls upcoming events by neighborhood using latitude, longitude, and a search radius, refreshing categories and formats so the feed stays current. Eventbrite returns structured event records with venue and timing, which the site renders as a browsable calendar.

Example prompt: Retrieve all events within a 10 mile radius of a set of coordinates and group them by category

### Interest-Based Event Alerts

A notification service watches for new events matching a user's chosen categories and price ceiling, querying Eventbrite on a schedule and alerting the user when a matching concert, workshop, or festival is announced. Filters on category, format, and price keep the alerts relevant.

Example prompt: Search for free workshops in a chosen category and return any new events added since the previous run

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/events/search/` | Search public events by location, date, category, and keyword |
| GET | `/events/{event_id}/` | Get full details for a single event by its id |
| GET | `/categories/` | List the Eventbrite event categories |

## Key resources

- **Events** — Search public events by location, date, and keyword, and retrieve full details including venue, organizer, and ticket availability
- **Categories** — List the Eventbrite category taxonomy used to filter and refine event searches

## Why Jentic

- **Setup:** Wiring the Eventbrite API by hand means registering an OAuth app, handling the bearer token, and building the location and date query parameters yourself. Through Jentic you install once, import Eventbrite from the API Directory, store the token once, and your agent calls the search and detail operations.
- **Permission scoping:** The Eventbrite endpoints are read-only event lookups, so a rule can bound your agent to just the search and single-event operations. You choose which operations it may call, so it can discover and read events and reach nothing more.
- **Credential handling:** Your Eventbrite bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search events by location' or 'get event details', and Jentic returns the matching Eventbrite operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **SeatGeek API** — SeatGeek surfaces live events and ticket listings for sports, concerts, and theater.
- **Ticketmaster Discovery API** — Ticketmaster Discovery searches large-venue events, attractions, and venues.
- **LocationIQ API** — LocationIQ geocodes an address into the coordinates Eventbrite search needs.

## FAQ

### What authentication does the Eventbrite API use?

The Eventbrite API authenticates with an OAuth 2.0 bearer token per its OpenAPI spec: you pass the token in the Authorization header as a bearer credential on each request. Through Jentic the token is stored once, encrypted, by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

### Can I search events by location with the Eventbrite API?

Yes. The event search operation accepts latitude, longitude, and a within radius, plus address, keyword, category, format, price, and start-date range filters, and returns matching public events. Retrieve a single event by its id to get venue, organizer, and ticket details.

### Is there an Eventbrite MCP server?

You don't need an MCP server to give your agent the Eventbrite API. Jentic connects it directly from the API Directory: import Eventbrite, store your token once, and your agent calls the event search and detail operations. Discovery happens on demand, so no extra server's tool definitions sit in the agent's context.

### Can I limit what my agent is allowed to do with the Eventbrite API?

Yes. Write a rule that permits only the event search and single-event read operations, so the agent can discover and read events but reach nothing else, and every call it makes is logged. You choose which operations it may call, so nothing beyond read access is included unless you add it.

### What are the rate limits for the Eventbrite API?

The OpenAPI spec does not specify rate limits. Check the Eventbrite platform documentation at https://www.eventbrite.com/platform for current limits and quota details.

### How do I search Eventbrite events through Jentic?

Import the Eventbrite API from the Jentic directory, store your bearer token once, and have your agent search with a query such as 'find events near a location'. Jentic returns the event search operation with its input schema so the agent supplies location and date filters and reads the results. To run it on your own infrastructure, install Jentic One from its GitHub repo.