Skip to content

Entitlements by plan

The API enforces the same plan as the app: a key sees exactly what a member of its organization sees. Entitlements are resolved from the organization’s subscription (or a custom Enterprise agreement) and apply to every key of the organization at once; a plan change takes effect on the next request, and open streams reconnect with close code 4409 to pick it up.

Every feature is free during the beta until December 1, 2026: every organization has Enterprise at no cost, so its keys get Enterprise's entitlements below. Organizations with a custom agreement keep it. The plans and prices apply once the beta ends.

EntitlementCoreProEliteEnterprise
Market data
Ticketmaster primary and TM resaleIncludedIncludedIncludedIncluded
Secondary marketplaces—IncludedIncludedIncluded
Sales history24 hUnlimitedUnlimitedUnlimited
Chart history30 daysUnlimitedUnlimitedUnlimited
Ended events——IncludedIncluded
% change filters——IncludedIncluded
Seat-map overlaysAvailabilityPrices and availabilityPrices and availabilityPrices and availability
Workflow
Compare events side by side4488
Lists525100Unlimited
Events per list1005002,000Unlimited
Alert rules25100UnlimitedUnlimited
Export rows—1,000UnlimitedUnlimited
Scalping predictions and track recordIncludedIncludedIncludedIncluded
API
REST API and stream—IncludedIncludedIncluded
Requests per minute—603001,200
Requests per day—5,00050,0005,000,000
Stream connections—1520
Subscriptions per connection—505002,000
Sales and on-sale firehose——IncludedIncluded
Webhooks——IncludedIncluded

Prices and trials are on the pricing page. An organization without an active plan can sign in and browse the catalog, but has no API access.

A request for something the plan doesn’t include answers 402 plan-required, naming the plan that allows it. Examples:

  • Metrics, series, sales, inventory changes, movers and compare need market data (every paid plan).
  • minChg24h / maxChg24h on GET /v1/events need Elite (percent_change_filters).
  • Market reads for an event that started more than 24 hours ago need Elite (ended_events): metrics, series, sales, sections, inventory changes and the section layers of the map overlay (mode).
  • Marketplace scopes (secondary:*) need Pro (secondary_sources). Asking for one (scope=secondary:best on movers, the sales summary, series, …) answers 402; reads that cover every market (GET /v1/events/{id}/metrics, GET /v1/sales/summary without scope) leave the marketplace rows out instead.
  • Creating a list, an alert rule or a list item beyond the plan’s count answers 402 with limit set to that count.
  • Alert rules are checked against the current plan whenever they are used, not only when written. After a downgrade or a lapsed plan, rules the plan no longer allows (their market scope or feature, or enabled rules past its count, counted oldest first) stop firing, and POST /v1/alerts/rules/{id}/test answers 402 for them. They resume once a plan allows them again.
  • Creating a webhook endpoint needs Elite (webhooks); exports need Pro (csv_export).

Sales history and chart history are windows back from now. A read that reaches further back than your window is clamped to it rather than refused:

  • GET /v1/events/{id}/series and GET /v1/compare/series start no earlier than the plan’s chart window. A range entirely outside it answers 402 series_history.
  • GET /v1/events/{id}/sales and GET /v1/sales/feed only return sales inside the plan’s sales window.
  • Test firings of activity rules (POST /v1/alerts/rules/{id}/test) list only changes inside the sales window, and none of events the plan may not read as ended.
  • On the stream, since replays at most as far back as the sales window; older gaps answer resync.

On plans without map prices, GET /v1/events/{id}/map/overlay returns availability only: open seats per section and per seat, without price levels. The section table and section series (GET /v1/events/{id}/sections, GET /v1/events/{id}/sections/{key}/series) follow the same rule: ticket and sales counts stay, and every price field (floor, median, average sale price, 24h change, spread, ROI, currency) is null.

API keys need Pro or higher. Request quotas, stream connections and subscriptions are listed above and explained in rate limits.

On the stream:

  • The sales and onsales firehose topics need Elite (firehose); subscribing on Pro answers an in-band forbidden_topic error. On Elite, API keys must bound them with a country/region, segment, eventIds/listId (sales) or attractionIds (onsales) filter; scope, source and minPrice don’t count (see filters). Unfiltered firehose subscriptions need Enterprise (unfiltered_firehose, api.firehoseUnfiltered in GET /v1/billing/plans). Signed-in app sessions are not limited by this rule.
  • Market topics (event.{id}.kpis, event.{id}.sales, event.{id}.primary) need market data; API keys subscribing to event.{id}.primary need market:read.
  • Messages are filtered to what the plan may see: sales of markets outside the plan are dropped, and KPI payloads only carry the plan’s markets.