canonical: https://jentic.com/apis/ticketmaster.com/commerce-api

# Ticketmaster Commerce API

Use the Ticketmaster Commerce API to look up available offers and products on various Ticketmaster platforms for North America markets. For formal partnerships and relationships, selected offers and products can be carted and transacted on through the cart, delivery, payment and purchase APIs - These APIs require approved access from Ticketmaster. The API exposes 1 endpoints.

## For AI agents

Programmatically event offers. Covers 1 operations.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Event Offers
- Manage payments data programmatically
- Integrate Commerce API into automated workflows
- Query and filter Commerce API records by parameters
- Monitor Commerce API operational status and events

## Use cases

### Payments Operations

Use the Commerce API to perform payments operations programmatically. The API provides 1 endpoints covering core functionality including event offers.

Example prompt: Call GET /commerce/v2/events/{eventId}/offers to event offers

### Data Retrieval and Monitoring

Query Commerce API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Commerce API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Commerce API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'event offers', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /commerce/v2/events/{eventId}/offers | Event Offers |

## Key resources

- **Commerce** — Operations for commerce

## Why Jentic

- **Setup:** Wiring the Ticketmaster Commerce API by hand means building the request to the discovery host and handling the offers response yourself, even though the offers endpoint takes no API credential. Through Jentic you install once, import the Commerce API from the API Directory, and your agent calls it.
- **Permission scoping:** This API exposes one read operation, GET /commerce/v2/events/{eventId}/offers, with the event id in the URL path, so a rule can pin your agent to offers for one event and nothing else. It has no write or delete operations to grant unless you add other APIs.
- **Credential handling:** This Commerce API operation takes no API credential, so there is nothing to store. Your own Jentic One instance still applies any required request handling at execution time, and nothing sensitive enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get ticket offers for an event', and Jentic returns the matching Commerce API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Commerce API use?

The Commerce API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I event offers with the Commerce API?

Yes. Use the GET /commerce/v2/events/{eventId}/offers endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Commerce API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I event offers through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'event offers'. Jentic returns the matching Commerce API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Commerce API have?

The Commerce API exposes 1 endpoints covering commerce operations.

### Can I limit what my agent is allowed to do with the Commerce API?

Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use, and this API exposes only one read operation, GET /commerce/v2/events/{eventId}/offers. Since the event id sits in the URL path, you can pin the agent to offers for a single event and nothing else. There are no write or delete operations to grant unless you add other APIs.