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

# Ticketmaster Discovery API

The Ticketmaster Discovery API allows you to search for events, attractions, or venues. The API exposes 13 endpoints.

## For AI agents

Programmatically attraction search, get attraction details. Covers 13 operations.

## Scope

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

## Capabilities

- Attraction Search
- Get Attraction Details
- Classification Search
- Query and filter Discovery API records by parameters
- Monitor Discovery API operational status and events

## Use cases

### CRM Operations

Use the Discovery API to perform crm operations programmatically. The API provides 13 endpoints covering core functionality including attraction search, get attraction details, classification search.

Example prompt: Call GET /discovery/v2/attractions to attraction search

### Automated v2 Management

Automate v2 operations by combining multiple Discovery API endpoints. Agents can get attraction details and then classification search in a single workflow.

Example prompt: Call GET /discovery/v2/attractions/{id} to get attraction details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Discovery 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 'attraction search', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /discovery/v2/attractions | Attraction Search |
| GET | /discovery/v2/attractions/{id} | Get Attraction Details |
| GET | /discovery/v2/classifications | Classification Search |
| GET | /discovery/v2/classifications/genres/{id} | Get Genre Details |
| GET | /discovery/v2/classifications/segments/{id} | Get Segment Details |
| GET | /discovery/v2/classifications/subgenres/{id} | Get Sub-Genre Details |
| GET | /discovery/v2/classifications/{id} | Get Classification Details |
| GET | /discovery/v2/events | Event Search |

## Key resources

- **v2** — Operations related to v2

## Why Jentic

- **Setup:** Wiring the Ticketmaster Discovery API by hand means building requests to the discovery host and handling the attraction, classification, and event responses yourself, even though these endpoints take no API credential. Through Jentic you install once, import the Discovery API from the API Directory, and your agent calls it.
- **Permission scoping:** Discovery puts the attraction and classification ids in the URL path (/discovery/v2/attractions/{id}), so a rule can pin your agent to one resource, and every operation is read-only search and lookup. You choose the operations it may call, so it stays limited to the lookups you grant.
- **Credential handling:** These Discovery API operations take 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 'search for attractions' or 'find events by classification', and Jentic returns the matching Discovery API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Discovery API use?

The Discovery 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 attraction search with the Discovery API?

Yes. Use the GET /discovery/v2/attractions endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Discovery 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 attraction search through Jentic?

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

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

The Discovery API exposes 13 endpoints covering v2 operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Discovery API operations the agent may call, and every operation here is read-only search and lookup such as GET /discovery/v2/attractions, GET /discovery/v2/classifications, and GET /discovery/v2/events. Since the attraction and classification ids live in the URL path (for example /discovery/v2/attractions/{id}), a rule can pin the agent to specific resources rather than the whole catalogue. You grant only the lookups you want, so the agent stays limited to exactly those calls.