Ticketmaster Discovery API

Name: Discovery API
Brand: Discovery API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact Managementnone13 EndpointsREST

For Agents

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

Use for: I need to attraction search, I want to attraction details, Search for classification search, Find all genre details

Install Jentic One Beta

Connect the Discovery API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Discovery API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Discovery API.

Attraction Search

Get Attraction Details

Classification Search

Query and filter Discovery API records by parameters

GET STARTED

Start building with Discovery API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Discovery API for, with concrete tasks.

★ 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.

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.

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.

Search Jentic for 'attraction search', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

13 endpoints — the ticketmaster discovery api allows you to search for events, attractions, or venues.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Discovery API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'attraction search') and Jentic returns the matching Discovery API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Discovery API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Discovery API through Jentic.

What authentication does the Discovery API use?

The Discovery API uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

Ticketmaster Discovery API

Connect the Discovery API to your agent

Capabilities

Start building with Discovery API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs