API Client Libraries
The following client libraries are excellent resources to help make Eventbrite integration quick and painless. Most web programming languages already have an API client available.
Language-specific usage examples are bundled with each of these libraries.
Is your language of choice missing from our list? Let us know!
Client Development Best Practices
If you are working on an open-source Eventbrite API client, please keep the following best practices in mind as you build:
- Include documentation and usage examples.
- Client functions that are named after EventbriteAPI calls, and that directly generate API requests, should allow parameters to be passed by-name or as key-value pairs.
- API request parameters should be automatically urlencoded. This is one of the most common sources of errors when constructing API requests.
- Consider including support for caching – Even though support for caching storage may vary per system, consider adding some optional support for this feature. It can greatly accelerate your application’s response time, and help keep your request volume within Eventbrite’s usage limits (default is 1000 requests per day).
If you are planning to use Eventbrite data in an application, please take a look at our branding guidelines and other 3rd party application requirements.
Developers using the Eventbrite API should review the API terms of service. By using the Eventbrite API, you are obligated to comply to the terms.