Skip to content
E-commerce platforms

ticketmaster.com:discovery

Discovery sandbox and mock API

The Ticketmaster Discovery API allows you to search for events, attractions, or venues. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
13
Collections
-
Event types
-
example request
curl https://your-ticketmaster-discovery.slurry.io/discovery/v2/discovery/v2/attractions \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version v2.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 13.

  • GET/discovery/v2/attractions
  • GET/discovery/v2/attractions/{id}
  • GET/discovery/v2/classifications
  • GET/discovery/v2/classifications/genres/{id}
  • GET/discovery/v2/classifications/segments/{id}
  • GET/discovery/v2/classifications/subgenres/{id}
  • GET/discovery/v2/classifications/{id}
  • GET/discovery/v2/events
  • GET/discovery/v2/events/{id}
  • GET/discovery/v2/events/{id}/images
  • GET/discovery/v2/suggest
  • GET/discovery/v2/venues