About the Eventbrite API
The Eventbrite REST API enables communication between Eventbrite and your application or website using HTTP requests. Transmitted request and response data content is formatted as JSON (although we provide a GET alternative for requests), using UTF-8 encoding and URL encoded values.
Base URL
All URLs referenced in the API documentation have the following base
https://www.eventbriteapi.com/v3
Authenticating Your Access to the Eventbrite API
HTTP requests to the Eventbrite API are protected by requiring authentication. To learn how, refer to Authenticating Your Access.
API Terminology
Knowledge of the following terms can help you successfully use the features and capabilities of the Eventbrite Platform.
Absorbed Fees
Eventbrite transaction fees included (absorbed) in the displayed ticket price; the credit card processing fees and taxes are not split out from the base ticket price.
Attendee
Individual holding a ticket to, and planning to attend, an Event.
Attendee Team
A grouping of Event attendees, for example a baseball team in a baseball tournament.
Bookmark
A visitor to the Eventbrite website has saved the Event as a bookmark.
Capacity
Maximum number of tickets that can be sold for an Event.
Category
The Event class, for example Music.
Endpoint
A URL that makes up part of the Eventbrite API; each resource is exposed at an API endpoint. These endpoints are used to integrate Eventbrite with other applications by accepting web requests.
Expansion
To limit the number of calls to the API, and the size of the responses, usually responses are short and display only a basic representation (subset) of the resource. However, you can obtain additional expanded information on certain elements by using an expansion.
Format
Type of event, for example conference, seminar, concert.
HTTP Verbs (Methods)
The Eventbrite API uses the following HTTP verbs (methods) appropriate for each action.
| HTTP Verb | Description | Example Action |
|---|---|---|
GET | Retrieve a resource | List all Events by Venue |
POST | Create or update a resource | Create or an Event |
DELETE | Delete a resource | Delete an Event |
Object
An object in the Eventbrite API that represents a business noun, like Event or Attendee. Also referred to as a resource.
Order Owner
Individual purchasing an Event ticket. Not necessarily an Attendee, as the Order Owner may be purchasing tickets for someone else.
Organization
An object representing a business structure (like a Marketing department) in which Events are created and managed. Organizations are owned by one User and can have multiple members.
Organizer
Object representing the public facing entity organizing the Event. Organizer does not have an Eventbrite account and does not own Events.
Pagination
Process of splitting up results into manageable chunks. All API endpoints that return results are paginated. These results are listed in a defined order in groups of 50, with the first page shown. To view additional result pages, you must specify in the request the page you want to see.
REST
A software architectural style. REST defines a set of constraints used for creating web services and manipulating resources. The Eventbrite API uses REST.
Subcategory
The Event subclass, for example Classical.
Ticket Class
A ticket type. Typically, multiple different types of tickets for an Event are available. There are three Eventbrite Ticket Classes: Free, Paid and Donation.
Ticket Price
The total ticket price is made up of the Ticket Base Price + Eventbrite Fee + Credit Card Fee + Tax.
User
Has an Eventbrite account, is a member of one or more Organizations, and may have the necessary permissions to create and manage Events.
Viewport
A rectangular section of a map, that is currently rendered, showing the Event location.
Visitor
A person viewing an Event on the Eventbrite website, but they have not yet become an Order Owner by purchasing tickets.