Ticketmaster Discovery API vs DICE for AI agents
Ticketmaster Discovery API is a REST API from Ticketmaster for searching events, attractions and venues sold on Ticketmaster and its related ticketing platforms. DICE is a GraphQL API for DICE's promoter and venue partners to query their own events, tickets, orders and ticket holders.
The short answer
- Ticketmaster Discovery API: Finding concerts, sports and theater events sold through Ticketmaster in North America and Europe, with a direct link to buy.
- DICE: Promoters selling on DICE who want to pull their own ticket and fan data into other systems.
Side by side
| Ticketmaster Discovery API | DICE | |
|---|---|---|
| Searches | Events, attractions (performers, teams) and venues across Ticketmaster, TicketWeb, Universe, FrontGate, Ticketmaster Resale and other Ticketmaster platforms; paging stops at the 1,000th item. | Only the partner's own events and related ticket, order and financial data. |
| Returns | Event name, dates, venue and location, attractions, price ranges, images and the Ticketmaster website URL for the event. | – |
| Before the first call | A Ticketmaster developer account and API key; access to the public APIs is instant after registration. Default quota is 5,000 calls a day (the getting-started page says 5 requests a second, the FAQ says 2). The bulk Discovery Feed and the Partner Commerce API need approval. | A DICE partner account; the API token is generated in DICE's partner tool (MIO). |
| Acting on a result | Ticket link: each event carries its Ticketmaster website URL. Approved affiliates (via Impact) get their tracking added to event links automatically; buying inside your own app needs the restricted Partner Commerce API. | – |
| Limits on keeping or showing results | Event content may be cached or stored only for reasonable periods needed to provide your service, and content must be removed within 24 hours if its owner asks. | – |
| Coverage | Global; the docs list the United States, Canada, Mexico, Australia, New Zealand, the UK, Ireland and other European countries. | – |
| MCP server | No official server listed | – |
Where Openpath fits
Openpath has no event listings yet. Events are on its roadmap, from organizers who list them themselves. Get listed.
Questions people ask
What do I need before I can use Ticketmaster Discovery API?
A Ticketmaster developer account and API key; access to the public APIs is instant after registration. Default quota is 5,000 calls a day (the getting-started page says 5 requests a second, the FAQ says 2). The bulk Discovery Feed and the Partner Commerce API need approval.
Is Ticketmaster Discovery API free?
Its pages listed no free use when we read them on October 15, 2026.
Sources
Every line about another company comes from its own pages. Prices and terms change, so check the source before you rely on one.
Ticketmaster Discovery API, read on October 15, 2026:
- developer.ticketmaster.com/products-and-docs/apis/discovery-api/v2: “The Ticketmaster Discovery API allows you to search for events, attractions, or venues.”
- developer.ticketmaster.com/products-and-docs/apis/discovery-api/v2: “This includes the venue and location, the attraction(s), and the Ticketmaster Website URL”
- developer.ticketmaster.com/products-and-docs/apis/discovery-api/v2: “Deep Paging: we only support retrieving the 1000th item.”
- developer.ticketmaster.com/products-and-docs/apis/discovery-api/v2: “United States, Canada, Mexico, Australia, New Zealand, United Kingdom, Ireland, other European countries, and more.”
- developer.ticketmaster.com/products-and-docs/apis/getting-started: “Event coverage is global.”
- developer.ticketmaster.com/products-and-docs/apis/getting-started: “Our APIs work against many platforms including Ticketmaster, TicketWeb, Universe, FrontGate, Ticketmaster Resale (TMR) and many more.”
- developer.ticketmaster.com/products-and-docs/apis/getting-started: “All API keys are issued with a default quota of 5000 API calls per day and rate limitation of 5 requests per second.”
- developer.ticketmaster.com/products-and-docs/apis/getting-started: “Upon registration and obtaining your API key, you will be able to access our Discovery and Commerce APIs instantly.”
- developer.ticketmaster.com/support/faq: “which come with a quota of 2 requests per second and 5000 requests per day.”
- developer.ticketmaster.com/support/faq: “Access to our Partner Commerce API is typically restricted to a select few business partners.”
- developer.ticketmaster.com/support/faq: “ensuring that your Impact tracking is automatically added to event links within the Discovery API/Feed.”
- developer.ticketmaster.com/support/terms-of-use: “Cache or store any Event Content other than for reasonable periods in order to provide the service you are providing.”
- developer.ticketmaster.com/support/terms-of-use: “Remove from your application within 24 hours any Event Content or other information or tickets that the owner asks you to”
DICE, read on October 15, 2026:
- partners-endpoint.dice.fm/graphql/docs/index.html: “The DICE Ticket Holders is a GraphQL API that allows downstream systems to query on a number of entities”
- partners-endpoint.dice.fm/graphql/docs/index.html: “related to a partner's events”
- partners-endpoint.dice.fm/graphql/docs/index.html: “Requests should be authenticated with API token.”