Skip to content

Changelog and deprecation policy

  • /v1 changes are additive only. New operations, new optional parameters, new response fields and new enum values can appear at any time. Ignore fields you don’t know, and handle enum values you don’t know (show them, log them, skip them), so these changes never break your integration.
  • A breaking change means /v2. Removing or renaming an operation, field or parameter, making a parameter required, or changing a type ships as a new version, run side by side with /v1 for at least 6 months.
  • Deprecations are announced first. No operation is deprecated today. Before anything is removed, it is announced here and marked deprecated: true in the OpenAPI spec.
  • Every change is checked. The public spec is generated from the API’s contract, and continuous integration runs an oasdiff backward-compatibility check against the last released spec; a breaking change fails the build.

The SDKs’ version is the version of the spec they were generated from.

Market-activity alerts and webhooks. Additive only.

  • Alert rules: a new condition type activity reports market activity change by change: primary.restock, primary.sale, resale.listed and resale.sold (Ticketmaster resale removals, which are most often sales but always low confidence), filtered by sections, minQuantity, minPrice / maxPrice (all-in) and, for primary sales, confidence. Rules gain a venue scope and a digestSeconds window (0, 30, 60 or 300 s) that merges bursts into one message per channel. Firings of activity rules list their changes in items / itemsTotal and link the Ticketmaster page in ticketUrl; deliveries gain dueAt and coalescedInto. See alerts.
  • New enum values in responses: activity (condition and firing kind), venue (scope kind), and the channel kinds slack_webhook, teams_webhook and google_chat_webhook in firing deliveries.
  • Webhooks: new event types inventory.restocked, inventory.sold, resale.listed and resale.sold for the events of an endpoint’s list, and an optional markets filter on endpoints. See webhooks.
  • SDKs 1.1.0 regenerated from the new spec.

2026-10-28: API 1.0.0, stream protocol 0.1.0, SDKs 1.0.0

Section titled “2026-10-28: API 1.0.0, stream protocol 0.1.0, SDKs 1.0.0”

The first public release of the client API.

  • REST API 1.0.0: catalog, search, calendar, event metrics, series, sales, the sales feed, movers, compare, seat maps and overlays, saved lists, alert rules and firings, webhooks, exports and usage. See the API reference.
  • API keys with scopes, IP allowlists, expiry, rotation with a grace period and revocation. See authentication.
  • Quotas per plan with RateLimit-Policy / RateLimit headers. See rate limits.
  • Realtime stream 0.1.0 with Bearer keys or tickets: event.{id}.kpis, event.{id}.sales, event.{id}.primary, sales, onsales and alerts. See the stream guide.
  • Webhooks: alert.fired, onsale.announced, event.status_changed, list.sale. See webhooks.
  • Exports of events, sales, series and lists to CSV or JSON Lines. See exports.
  • SDKs: @status302/sdk 1.0.0 and status302 1.0.0 for Python.