canonical: https://jentic.com/apis/ticketmaster.com

# Ticketmaster APIs

Ticketmaster is a live-events ticketing platform. Its APIs let agents search events, attractions, venues, and classifications, publish and update attraction and event listings, and look up ticket offers for events across North American markets.

## For AI agents

Across Ticketmaster's APIs an agent can search events, attractions, and classifications, publish or patch attraction and event listings, attach videos to them, and look up available ticket offers for a given event.

## Scope

Use for: Searching Ticketmaster events, attractions, venues, and classifications, publishing or updating attraction and event listings, and looking up available ticket offers for an event

Not supported:
- cart checkout
- payment processing
- ticket delivery
- seat map rendering
- resale marketplace

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Discovery API | crm | 13 | Programmatically attraction search, get attraction details. |
| ticketmaster publish API | crm | 10 | Programmatically publish an attractions, publish a patch on an attraction. |
| Commerce API | payments | 1 | Programmatically event offers. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Search and read events, attractions, venues, and classifications | discovery | Discovery is the read side, with search and lookup endpoints for attractions, events, and classification genres and segments. |
| Create or update attraction and event listings, including video | publish | Publish is the write side, with POST and PATCH endpoints for attractions, events, entitlements, and extensions. |
| Look up available ticket offers for a specific event | commerce | Commerce exposes the offers lookup for an event id and is the only offer-oriented API in the set. |

## Cross-API use cases

### Publish a listing then confirm it in search

Create an attraction or event with the publish API, then read it back through the discovery API to confirm it appears in search and lookup results.

Example prompt: Call POST /publish/v2/attractions to create the attraction, then GET /discovery/v2/attractions to confirm it is searchable

### Find an event and pull its ticket offers

Search the discovery API for a matching event, take its event id, and look up the available ticket offers for that event through the commerce API.

Example prompt: Call GET /discovery/v2/events to find the event, then GET /commerce/v2/events/{eventId}/offers for its offers

### Publish an event and check its offers

Create an event through the publish API, then query the commerce API for the ticket offers attached to that event id.

Example prompt: Call POST /publish/v2/events to create the event, then GET /commerce/v2/events/{eventId}/offers to read its offers

## Why Jentic

- **Setup:** Calling the Discovery, Publish, and Commerce APIs by hand means wiring requests to the Ticketmaster discovery host and parsing attraction, event, and offer responses for each one. With Jentic you install once and your agent adds any of the three from the Jentic directory, then calls them the same way.
- **Permission scoping:** The read, publish, and offer operations are separate, and attraction and event ids sit in the URL path. Your own rules in your Jentic One instance decide which operations the agent may call, so you can grant read-only discovery and offer lookups while withholding the publish write actions until you add them.
- **Credential handling:** These APIs are documented with no authentication, so there is nothing to store for them, but any request handling still runs inside your own Jentic One instance and nothing sensitive enters the agent's prompt, logs, or context. If you later add authenticated Ticketmaster partner endpoints, their credentials are stored encrypted in your instance.
- **Discovery method:** An agent searches Jentic by intent, such as 'search events', 'publish an attraction', or 'get ticket offers for an event', and Jentic returns the matching Ticketmaster operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related vendors

- **Eventbrite** — Event listing and ticketing platform, an alternative for event search and publishing.
- **SeatGeek** — Event discovery and ticket marketplace covering similar live-event inventory.
- **StubHub** — Ticket marketplace for events, complementary for offer and resale lookup.
- **Songkick** — Concert and event discovery data, adjacent to Ticketmaster event search.

## FAQ

### What can an agent do across Ticketmaster's APIs?

An agent can search events, attractions, venues, and classifications, publish and update attraction and event listings and attach videos to them, and look up the ticket offers available for a given event.

### Do the Ticketmaster APIs share one credential?

The OpenAPI specs for all three APIs document no authentication, so there is no single shared secret to manage across them. Some commerce and transaction flows do require approved partner access from Ticketmaster.

### Which Ticketmaster API should I start with?

Start with the Discovery API when you need to read or search events, attractions, and classifications. Use the Publish API to create or update listings, and the Commerce API to look up ticket offers for an event.

### Can these APIs work together in one workflow?

Yes. A common pattern is to publish a listing, confirm it in discovery search, then read the ticket offers for the event through commerce, chaining the three APIs by event and attraction id.

### Do the Ticketmaster APIs handle checkout or payment?

No. The offers endpoint only surfaces available offers. Carting, delivery, payment, and purchase run through separate Ticketmaster APIs that require approved partner access and are outside this set.

### Which regions do these APIs cover?

The Commerce API documents coverage of North American markets for offer and product lookup. Confirm regional coverage for search and publish against Ticketmaster's own documentation.