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. The exception is a change required by law, by a security issue or by a data source outside our control (the Terms, §6.3): it ships in /v1 as a minor release, announced here as a correction.
  • 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, with its deprecation date and a sunset date at least 6 months later. Every response of a deprecated operation, errors included, carries Deprecation: @<unix seconds> (RFC 9745), Sunset: <HTTP date> (RFC 8594) and Link: <…>; rel="deprecation" pointing at the announcement; browsers can read them (CORS exposes them). Log them in your client to find calls to migrate.
  • 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.

Additive only.

  • Managed lists: a saved list can now carry managedBy, set when the app keeps the list itself (sales: the Sales Manager list, which holds your accepted Sales Manager tickets with their quantity and average cost, so they count in the portfolio). Adding, changing or removing a managed list’s items, or deleting the list, answers 409; you can still rename it and change its view. canDelete is false for a managed list.
  • SDKs 1.9.0 regenerated from the new spec.

Additive only.

  • Venue directory: GET /v1/venues lists every catalog venue, most upcoming events first, then by name, with cursor pagination (limit up to 100, default 50), a name filter q (folded like GET /v1/search) and a country filter. Each venue carries its city, state and country, its number of upcoming events (refreshed every few minutes) and its next event’s start (nextStartsAt).
  • SDKs 1.8.0 regenerated from the new spec, with listVenues (list_venues, ListVenues).

2026-11-13: TM resale in 12 European countries

Section titled “2026-11-13: TM resale in 12 European countries”

Additive only, no new API version.

  • TM resale in Europe: tm_resale now covers events Ticketmaster hosts in Poland, Spain, Czechia, the Netherlands, Austria, Belgium, Germany, Denmark, Norway, Sweden, Finland and Switzerland (ticketmaster.pl, .es, .cz, .nl, .at, .be, .de, .dk, .no, .se, .fi and .ch), besides the US, Canada, the UK and Ireland, with listings and prices in each site’s currency (EUR, PLN, CZK, DKK, NOK, SEK, CHF). Their TM resale links use the site’s code and the number at the end of the event’s Ticketmaster URL as external id (de:1385439776). Their listings name the level and section, row and seats; they have no seat map places.
  • Coverage in the sales summary: tracked is now true for tm_resale in those countries.

Additive only, with a new checking cadence.

  • Event tiers: EventTier (tier of event rows and the tier filter of GET /v1/events) gains hot. Events are checked every 15 minutes while one of your alert rules covers them (watched, until they start), hourly while hot (read in the last 24 hours), and otherwise (standard) every 3 hours on their on-sale day and in the 48 hours before they start, daily or less often the rest of the time (slower for events far out or without market activity). Add-on listings such as parking passes, upgrades and vouchers are dormant.
  • Marketplace matching: an event not linked to a marketplace yet is searched when it appears and then at its sale starts and 30, 7 and 1 days before the show, every 6 hours while watched or hot; a read also searches it when the last search is over 6 hours old.
  • Reads heat events: reading an event with your API key (GET /v1/events/{id} and its own sub-resources) keeps it hot for 24 hours and refreshes data older than 10 minutes in the background; the response is never delayed, and the new data arrives on the event’s stream topics. Each organization heats at most its plan’s number of hot events per rolling day; further events are served without heating. Batch reads (GET /v1/events?ids=, listId), catalog, search and exports don’t heat.
  • SDKs 1.7.0 regenerated from the new spec.

Two content-licensing corrections. Event, attraction and venue images belong to Ticketmaster and DICE, and the venue drawings to Ticketmaster; the web app still shows the images, and nothing else passes them on.

  • Removed (breaking, correction): responses to API keys no longer carry imageUrl (events, search, attractions, venues, calendar, lists, portfolio, movers, predictions, must cops), and the event summary of sales and alert firings (SaleEventRef) no longer has it at all. Webhook payloads (alert.fired, onsale.announced, market activity), stream messages (sales, event.{id}.sales, onsales) and export files carry no image URL either. The SDKs’ types no longer declare it.
  • Changed (correction): GET /v1/seatmaps/{hash} serves .tmap format 2 (Seatmap.format is 2). Section outlines are generated from the seats (a seated section) or the section’s extent (general admission, stage), and the artifact has no labels, label styles or image tiles: draw section names yourself. Sections, rows, seats and their place indexes are unchanged, so overlays keep their keys. Format 1 artifacts were deleted; their hashes and cdnUrls answer 404, and each event links to its format 2 map after its next map poll (status: pending until then).
  • Notifications: Discord, Slack and Google Chat messages no longer show the event’s image.

Additive only.

  • Batch event reads: GET /v1/events takes ids (comma-separated, at most 200; more is a 400) and listId (a saved list of your organization; 404 otherwise). Both narrow the catalog query and keep every other filter, sort and metric scope, so a watchlist is one request instead of one per event.
  • More conditional reads: event sections, section series, price levels, offers, ticket types, listing and sales sections, attraction history, predictions (calls, track record, availability), lists (index, list, items) and the portfolio (and its history) answer If-None-Match with 304. Browsers can now read ETag on cross-origin responses (CORS exposes it), so the SDKs’ ETag cache works there too.
  • Must cops on the API: GET /v1/must-cop accepts API keys with market:read, under the same plan and publication rules as the app.
  • Alert rules:
    • Metric conditions take spread (resale and secondary markets only; primary is a 400) and churn24h.
    • PUT /v1/alerts/rules/{ruleId}/snooze ({until}, at most 90 days ahead) and DELETE …/snooze pause a rule without disabling it; AlertRule.snoozedUntil is set while a snooze runs, and a snoozed match records the skip reason snoozed.
    • New activity kinds: primary.type_on_sale, primary.type_added, primary.waitlist and primary.price_change (DICE ticket types) and primary.pulled (Ticketmaster seats gone inside the cart-hold window; requires minQuantity). activities no longer declares maxItems: it is bounded by the kinds themselves.
    • Catalog condition onsale_reminder (leadMinutes 15, 60, 180 or 1440; includePresales) fires once per on-sale before it starts.
    • Condition type: pick (kind mustcop or prediction, optional category and maxRisk) fires when a pick opens; picks are model output, not financial advice.
  • SDK errors carry the response’s request id (ApiError.requestId, APIError.request_id), also appended to the message.
  • Go SDK: github.com/status403com/status302-go v1.5.1 (guide), with the same REST client (typed methods, retries, pagination iterators, typed errors, conditional requests and ETag cache), stream client and webhook verification as the other SDKs.
  • TM resale in the UK and Ireland: tm_resale now covers events Ticketmaster hosts in the UK and Ireland (ticketmaster.co.uk and ticketmaster.ie), besides the US and Canada, with listings and prices in GBP and EUR. Their TM resale links use the external id uk:<event id> or ie:<event id>. Australia, New Zealand and Mexico have no Ticketmaster resale.
  • Coverage in the sales summary: each GET /v1/sales/summary market carries tracked, false when no source collects that scope in the requested country or region (e.g. tm_resale in Australia), so its zeros mean “not collected” rather than “no sales”.
  • Sales summary windows: GET /v1/sales/summary takes window (1h, 6h, 24h by default, 72h or 7d) and echoes it in the response. Up to 24h the window starts exactly that long before now; 72h and 7d start at the UTC hour holding that instant (see from). A window longer than your plan’s sales history is a 402.

2026-11-10: TM resale is Ticketmaster’s resale order book

Section titled “2026-11-10: TM resale is Ticketmaster’s resale order book”

TM resale (tm_resale) is now built from Ticketmaster’s resale listings: asking and all-in prices per listing, section, row and seats, and sales inferred from listings that sell out or disappear (kinds partial and removal). Before, it came from seat statuses priced at face value and stayed empty in practice.

  • One market: the secondary:tmresale scope, briefly listed among the marketplaces, is gone; its data is tm_resale. It is not part of secondary:best and does not need the secondary-marketplaces plan. Saved alert, webhook, list and preference settings that named it now name tm_resale.
  • Listings and sales: GET /v1/events/{id}/listings?market=tm_resale returns TM resale listings; TM resale sales carry source ticketmaster and scope tm_resale in the sales feed, streams and webhooks. resale.listed and resale.sold fire on those listings and sales.
  • Removed (breaking, released as a correction of always-empty data): GET /v1/events/{id}/inventory/changes no longer accepts market=tm_resale or the kinds resale_listed and resale_removed, which never returned rows; it reports primary inventory only.

2026-11-09: Daily API quotas on Pro and Elite

Section titled “2026-11-09: Daily API quotas on Pro and Elite”

No schema change; plan quotas changed.

  • Daily quotas: Pro includes 5,000 requests per day (was 50,000) and Elite 50,000 (was 500,000). Minute, concurrency and stream limits are unchanged, and so is Enterprise. While the free beta runs every organization is on Enterprise, so this applies once it ends. A key’s own requestsPerDay above its plan’s quota is capped by the organization’s. See rate limits.

No schema change; plan features changed.

  • Predictions for everyone: every plan now includes predictions, their track record and the must cops (PlanFeatures.predictions is true on Core and Pro too, and GET /v1/predictions no longer answers 402); a category is still shown once it is published. Predictions are model output, not financial advice. See predictions.

2026-11-08: Every sale counts; predictions graded on resale sales

Section titled “2026-11-08: Every sale counts; predictions graded on resale sales”

No schema change; defaults and the meaning of a graded call’s exit changed.

  • Every confidence by default: GET /v1/events/{id}/sales, GET /v1/sales/feed, GET /v1/sales/summary and the sales stream topic now include every sale (confirmed, inferred_high and inferred_low) unless confidence narrows them; the feed and the summary used to default to confirmed,inferred_high. Marketplace sales counts, volume and average sale price in metrics, series and section tables count low-confidence sales too. The confidence field and filter are unchanged.
  • Alert rules: an activity rule’s confidence defaults to any (every sale). Rules saved with high were moved to any; set high again to keep only high-confidence sales.
  • Sales, not listings: a call’s exit is now the median price of the resale sales between the call and the event (marketplaces and Ticketmaster resale), no longer the median resale floor of the last 72 hours, so a single overpriced listing can’t make a hit. A call with fewer than 3 resale sales is void.
  • Past calls regraded: calls graded under the old rule are regraded under the new one, keeping their gradedAt; some hits and misses become voids, and the track record changes with them. See predictions.

DICE predictions. Additive only.

  • Prediction categories: calls come in two categories, tm (Ticketmaster events) and dice (DICE events, a model of its own). GET /v1/predictions and GET /v1/predictions/track-record take an optional category (tm by default; an unknown value is a 400). PredictionCall.category and PredictionTrackRecord.category say which one a call or track record belongs to.
  • Per-category availability: PredictionAvailability.categories lists each category’s available, reason, currentModel, graded and minGraded, tm first; the top-level fields keep describing tm. Each category is published separately. See predictions.
  • SDKs 1.4.0 regenerated from the new spec.

Additive only.

  • Channel kind slack_app: GET /v1/channels and GET /v1/alerts/options (channelKinds) can return Slack channels the Slack app posts to. They are added from Settings → Integrations, not with POST /v1/channels; route rules to them by id like any other channel.

More of the app for API keys. Additive only.

  • Portfolio (catalog:read): GET /v1/portfolio, GET /v1/portfolio/export.csv and GET /v1/portfolio/history. See portfolio.
  • Alert preview and test firings (alerts:write): POST /v1/alerts/rules/preview and POST /v1/alerts/rules/{ruleId}/test. See alerts.
  • Notification channels (alerts:write): GET/POST /v1/channels, PATCH/DELETE /v1/channels/{channelId}, and its test, verify and verification operations; changes need an owner’s or admin’s key. See alerts.
  • Predictions (market:read, Elite): GET /v1/predictions, GET /v1/predictions/track-record and GET /v1/predictions/availability. See predictions.
  • SDKs 1.3.0 regenerated from the new spec, with:
    • Alert pagination: paginate / pages follow nextBefore as before, so GET /v1/alerts/rules and GET /v1/alerts/events (Python list_alert_rules, list_alert_events) walk every page instead of stopping after the first.
    • Conditional requests: operations accepting If-None-Match take ifNoneMatch / if_none_match; a 304 returns a typed NotModified instead of throwing. Responses expose their etag (Python: with_response.<operation> returns the whole APIResponse), and the opt-in etagCache / etag_cache (MemoryETagCache) revalidates GETs and returns the stored body on 304. See conditional requests.

2026-11-03: Marketplace rows on the map overlay

Section titled “2026-11-03: Marketplace rows on the map overlay”

Additive only.

  • Map overlay: with mode, every marketplace section layer (secondary:<source>, secondary:best) gives each section’s rows: its tickets by the row the listings name (empty row for listings naming none), with seated tickets and their seat label ranges (seats) or artifact place indexes (places), so a map can light exact seats, else the row, else the section. The ETag with mode also changes when a marketplace’s listings change.

Additive only.

  • Per-key quotas: API keys gain optional requestsPerMinute / requestsPerDay; 429 problems gain the limit values key_minute and key_day. See rate limits.
  • Members may manage API keys: Org.membersManageKeys; GET /v1/api-keys returns canManage, planRequestsPerMinute and planRequestsPerDay. See authentication.
  • Stream: ?encoding=msgpack sends binary MessagePack frames. Elite API keys must filter the sales / onsales firehoses; unfiltered firehose subscriptions are Enterprise’s (api.firehoseUnfiltered). See the stream guide.
  • Deprecation headers (Deprecation, Sunset, Link) on deprecated operations, as described above.

Why a rule didn’t fire. Additive only.

  • Alert rules gain an optional lastSkip (at, reason plan or cooldown, detail, and until for a cooldown, feature / requiredPlan for the plan): the rule matched but your plan doesn’t allow it, or it was in its cooldown. Cleared when the rule fires. See alerts.
  • SDKs 1.2.0 regenerated from the new spec.

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.