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

# Eventbrite API

Jentic publishes the only available OpenAPI specification for Eventbrite API, keeping it validated and agent-ready. The Eventbrite API creates and manages events, publishes them to an organization, and reads back the orders, attendees, and ticket classes attached to each one. It also searches the public event listings and manages the venues an organization uses, so an agent can run the full lifecycle of an event from creation through attendee lookup against a Bearer-authenticated account.

## For AI agents

Create, update, publish, and search events, read their orders, attendees, and ticket classes, and manage an organization's venues across 14 endpoints.

## Scope

Manages events, ticket classes, venues, and reads orders and attendees. Does not process payments, issue refunds, or handle payout settlement.

## Capabilities

- Create, update, publish, and delete events under an organization
- List and search events, including the public event search surface
- Read attendees, orders, and ticket classes for a given event
- Create ticket classes to define pricing and capacity for an event
- List and create venues an organization reuses across events
- Look up the authenticated user and organization context

## Use cases

### Agent-run event setup

An AI agent creates an event under an organization, adds ticket classes with pricing and capacity, and publishes it so registration opens, all from a single conversational instruction rather than clicking through the Eventbrite organizer dashboard.

Example prompt: Create an event titled 'Product Launch' for the organization, add a 100-capacity ticket class priced at 25, and publish it

### Attendee and order lookup

An agent answers organizer questions by reading the attendees and orders on an event, returning who registered and what was purchased so a support assistant can resolve queries without opening the web console.

Example prompt: List every attendee for event 123456789 and summarize how many tickets were sold per ticket class

### Event discovery assistant

An agent searches the public event listings by keyword and location and returns structured results so a user can find and compare upcoming events in a conversation.

Example prompt: Search Eventbrite for music events happening this month and return the top five by start date

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/events/search/` | Search the public event listings by keyword and filters |
| POST | `/organizations/{organization_id}/events/` | Create an event under an organization |
| POST | `/events/{event_id}/publish/` | Publish an event so it goes live |
| GET | `/events/{event_id}/attendees/` | List the attendees for an event |
| GET | `/events/{event_id}/orders/` | List the orders placed against an event |
| POST | `/events/{event_id}/ticket_classes/` | Create a ticket class for an event |

## Key resources

- **Events** — Create, update, publish, delete, and search events
- **Attendees** — Read who has registered for a given event
- **Orders** — Read the orders placed against an event
- **Ticket classes** — Define pricing and capacity tiers for an event
- **Venues** — Manage the venues an organization reuses across events

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 73 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 79 / 100
- **View full report:** https://jentic.com/apis/eventbrite.com/eventbrite/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Eventbrite by hand means registering an OAuth application, carrying a Bearer token on every call, and paging through events, orders, and attendees yourself. Through Jentic you install once, import the Eventbrite API from the Directory, store the token once, and your agent calls it.
- **Permission scoping:** The event and organization ids are path parameters, so scope by operation and by resource: allow the agent the read-only listing and lookup operations it needs while withholding create, update, delete, and publish, or confine it to one organization's events.
- **Credential handling:** Your Eventbrite OAuth token credential 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 'publish a new event' or 'list the attendees for an event', and Jentic returns the matching Eventbrite API operation with its input schema so the agent calls the right endpoint without reading the reference docs by hand.

## Related APIs

- **Ticketmaster Discovery API** — Discovery of primary-market events and ticket inventory rather than self-published events
- **SeatGeek API** — Event and ticket discovery across a secondary marketplace
- **Meetup API** — Community group events alongside ticketed Eventbrite events

## FAQ

### Why is there no official OpenAPI spec for Eventbrite API?

Eventbrite documents its API but does not publish a machine-readable OpenAPI specification. Jentic generates and maintains this spec, validates it against the live API, and keeps it current so agents and developers can call Eventbrite through structured tooling. To get started, install the self-hosted Jentic One runtime from its GitHub repository and import the Eventbrite API from the Jentic API Directory.

### What can an AI agent do with the Eventbrite API?

An agent can create, update, publish, and delete events, read their attendees, orders, and ticket classes, search public listings, and manage an organization's venues, covering the event lifecycle end to end.

### What authentication does the Eventbrite API use?

Requests carry an OAuth 2.0 Bearer token issued by Eventbrite. Jentic One stores that token encrypted in your own instance and attaches it at execution time.

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

Yes. Because event and organization ids are path parameters, you can scope the agent by operation and by resource: permit read-only listing and lookups while withholding the create, update, delete, and publish operations, or restrict it to a single organization's events.

### Does the Eventbrite API handle payments or refunds?

No. The spec reads orders and attendees and manages events, ticket classes, and venues, but it does not process payments, issue refunds, or move funds.