Skip to content
E-commerce platforms

ticketmaster.com:publish

ticketmaster publish sandbox and mock API

Publish API Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
10
Collections
-
Event types
-
Start this simulation
example request
curl https://your-ticketmaster-publish.slurry.io/ \
  -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

All 10.

  • POST/publish/v2/attractions
  • PATCH/publish/v2/attractions/{id}
  • POST/publish/v2/attractions/{id}/videos
  • POST/publish/v2/entitlements
  • POST/publish/v2/events
  • PATCH/publish/v2/events/{id}
  • POST/publish/v2/events/{id}/videos
  • POST/publish/v2/extensions
  • POST/publish/v2/venues
  • PATCH/publish/v2/venues/{id}