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.
| Entitlement | Core | Pro | Elite | Enterprise |
|---|---|---|---|---|
| Market data | ||||
| Ticketmaster primary and TM resale | Included | Included | Included | Included |
| Secondary marketplaces | — | Included | Included | Included |
| Sales history | 24 h | Unlimited | Unlimited | Unlimited |
| Chart history | 30 days | Unlimited | Unlimited | Unlimited |
| Ended events | — | — | Included | Included |
| % change filters | — | — | Included | Included |
| Seat-map overlays | Availability | Prices and availability | Prices and availability | Prices and availability |
| Workflow | ||||
| Compare events side by side | 4 | 4 | 8 | 8 |
| Lists | 5 | 25 | 100 | Unlimited |
| Events per list | 100 | 500 | 2,000 | Unlimited |
| Alert rules | 25 | 100 | Unlimited | Unlimited |
| Export rows | — | 1,000 | Unlimited | Unlimited |
| Scalping predictions and track record | Included | Included | Included | Included |
| API | ||||
| REST API and stream | — | Included | Included | Included |
| Requests per minute | — | 60 | 300 | 1,200 |
| Requests per day | — | 5,000 | 50,000 | 5,000,000 |
| Stream connections | — | 1 | 5 | 20 |
| Subscriptions per connection | — | 50 | 500 | 2,000 |
| Sales and on-sale firehose | — | — | Included | Included |
| Webhooks | — | — | Included | Included |
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.
How limits apply
Section titled “How limits apply”Gated features answer 402
Section titled “Gated features answer 402”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/maxChg24honGET /v1/eventsneed 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:beston movers, the sales summary, series, …) answers402; reads that cover every market (GET /v1/events/{id}/metrics,GET /v1/sales/summarywithoutscope) leave the marketplace rows out instead. - Creating a list, an alert rule or a list item beyond the plan’s count answers
402withlimitset 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}/testanswers402for them. They resume once a plan allows them again. - Creating a webhook endpoint needs Elite (
webhooks); exports need Pro (csv_export).
History windows clamp
Section titled “History windows clamp”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}/seriesandGET /v1/compare/seriesstart no earlier than the plan’s chart window. A range entirely outside it answers402 series_history.GET /v1/events/{id}/salesandGET /v1/sales/feedonly 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,
sincereplays at most as far back as the sales window; older gaps answerresync.
Map overlays
Section titled “Map overlays”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 access
Section titled “API access”API keys need Pro or higher. Request quotas, stream connections and subscriptions are listed above and explained in rate limits.
On the stream:
- The
salesandonsalesfirehose topics need Elite (firehose); subscribing on Pro answers an in-bandforbidden_topicerror. On Elite, API keys must bound them with acountry/region,segment,eventIds/listId(sales) orattractionIds(onsales) filter;scope,sourceandminPricedon’t count (see filters). Unfiltered firehose subscriptions need Enterprise (unfiltered_firehose,api.firehoseUnfilteredinGET /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 toevent.{id}.primaryneedmarket: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.
© 2026 status403 Sp. z o.o.Aleja Solidarności 68/121, 00-240 Warsaw, PolandKRS 0001269943NIP 5253108931Share capital PLN 5,000.00
Registry court: District Court for the Capital City of Warsaw, 12th Commercial Division

