Getting Started with the Eventbrite API
Eventbrite is the leading web-based solution for creating, managing, and promoting local events.
Whether you are interested in including adding robust event-management features to an existing site, or you want to include the best free event content in your application – the Eventbrite API can be your solution for accessing extremely rich and relevant local data.
Although our public event data is available without cost, we ask that you respect our user’s privacy, and comply with our data-usage terms when accessing and using our data.
If you’re ready to get started on the Eventbrite API, the best place to start is with the documentation of our endpoints.
API Request Limits
New API keys start out with a default rate-limit of 1000 requests per day, so please remember to swap in your own Application key when copying example request URLs from our interactive docs.
If you think you may be in danger of exceeding your request-limit threshold, feel free to contact us with an estimate of your anticipated API activity. We should be able to increase your limit to meet your application’s needs.
It’s now easier than ever to see a visual representation of the data that Eventbrite will return for an API call. We’ve made it easier for you to explore our API by creating a view that renders a very user friend API return right in your browser. To see an example, you can construct an API call from our documentation, or see this example here: https://www.eventbriteapi.com/v3/events/10584525601/?token=BKKRDKVUVRC5WG4HAVLT
Constructing API Request URLs
Eventbrite API request URLs are composed of the following components:
|protocol||http or https. SSL-encrypted https connections are definitely preferred.|
|hostname||Our API services are available on our www.eventbriteapi.com domain.|
|data-type||Only json is supported as a data-type.|
|API method||Navigate our API method pages to find out which service call will provide the data you need.|
|Authentication tokens||Each of our supported authentication schemes are covered on our authentication page.|
|request parameters||Key/Value pairs of request data, as defined in each of our API method pages.|
Put all these pieces together in order, and you should end up with a URL that looks something like this: