ticketmaster publish api

Can I publish an attractions with the ticketmaster publish API?

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

What are the rate limits for the ticketmaster publish 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 publish an attractions through Jentic?

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

How many endpoints does the ticketmaster publish API have?

The ticketmaster publish API exposes 10 endpoints covering publish operations.

Can I limit what my agent is allowed to do with the Ticketmaster Publish API?

Yes. Because you run Jentic One yourself, your own rules decide which of the publish operations the agent may call, so you can allow only read-safe intents and leave out write actions like POST /publish/v2/attractions, PATCH /publish/v2/events/{id}, or attaching a video until you explicitly add them. Since the attraction and event ids sit in the URL path, such as /publish/v2/attractions/{id} and /publish/v2/events/{id}, a rule can pin the agent to a single resource rather than the whole catalogue. The operator controls the full operation list, from entitlements to extensions, at execution time.