Everything you need to get up and running with the Ticketmaster API. Basic concepts are talked about here, so please keep reading :)
To get the most out of your experience, register for an API or log in to your account now. We’ll render links in examples and code samples into active link using your own API Key. If you prefer to jump right into the APIs and make live calls, check out the API Explorer.
We currently offer event discovery and commerce APIs with various access tiers. Upon registration and obtaining your API key, you will be able to access our Discovery and Commerce APIs instantly. Using both APIs allows you to create a meaningful event discovery experience for your fans.
Our APIs work against many platforms including Ticketmaster, TicketWeb, Universe, FrontGate, Ticketmaster Resale (TMR) and many more.
Event coverage is global.
Here’s a few examples of common use cases that most developers build apps against:
|Discovery API||Searching events by keyword in a certain location (lat/long).|
|Discovery API||Getting events for a particular artist OR venue in a specific country/city/zip code/DMA/etc.|
|Discovery API||Getting hi-res images for a particular event or artist.|
|Discovery API||Search events of a certain genre in a particular location for a certain promoter.|
|Commerce API||Get available offers for a particular event.|
|Partner API||Transact against offers for a particular event (partners-only).|
|Inventory Status API||Provides event status for primary Ticketmaster inventory with inventory.|
All API calls follow this format:
||A bucket that provides access to logically-related resources||Yes||discovery, commerce, accounts, etc|
||The package version||Yes||v1, v2, v3, etc|
||Path to API method||Yes||Varies per API call|
||Authorized API Key||Yes||Get your API key|
All API keys are issued with a default quota of 5000 API calls/day. We do increase rate limits on case-by-case basis. In order to increase the rate limit for a particular application, we need to verify the following:
- The application is in compliance with our Terms of Service
- The application is in compliance with our branding guide
- The application is representing the Ticketmaster data properly
Once these three criteria are verified, the rate limit is increased to what Ticketmaster and the developer determine to be appropriate.
Rate Limit Info in Response Header
You can see how much of your quota has been used by checking the following response headers:
- Rate-Limit: What’s the rate limit available to you. The default is 5000.
- Rate-Limit-Available: How many requests are available to you. This will be 5000 minus all the requests you’ve done.
- Rate-Limit-Over: How many requests over your quota you’ve made.
- Rate-Limit-Reset: The UTC date and time of when your quota will be reset.
API Response When Quota is Reached
When you do go over your quota, you will get an HTTP status code 429 indicating you’ve made too many requests. The following is the API response you will receive: