Ticketmaster Discovery API

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.