Skip to content

Status302 developer docs

Status302 tracks the Ticketmaster catalog and every event’s primary inventory, TM resale and sales. The web app is built on the same API you get: the catalog, metrics, series, sales, the calendar, seat maps, lists and alerts are all public operations, and every number the app shows live arrives over the same WebSocket stream.

  • Dashboards and pricing tools on event metrics (floor, median, inventory, sales, sell-through) per market, with their time series.
  • Live trading feeds from the stream: every sale, every primary inventory change and every newly announced on-sale, in order and resumable.
  • Automations on webhooks: your alert rules firing, on-sales announced, events postponed or cancelled, sales on events you hold.
  • Bulk pulls with async exports to CSV or JSON Lines instead of long paging loops.
Surface Use it for Auth
REST, https://api.status302.com/v1/… Reads and writes: catalog, metrics, lists, alert rules, webhooks, exports Authorization: Bearer <key>
Stream, wss://api.status302.com/v1/stream Live updates with replay after reconnects The key on the upgrade, or a single-use ticket
Webhooks Events pushed to your HTTPS endpoint, signed You verify the Status302-Signature header

API access starts with the Pro plan; the sales firehose and webhooks need Elite. See entitlements by plan.

  • JSON bodies use camelCase. Timestamps are RFC 3339 in UTC.
  • Money is an integer amount in minor units with an ISO 4217 currency code. See money and currency.
  • Lists are cursor-paginated: pass the response’s nextCursor back as cursor. See pagination.
  • Errors are RFC 9457 application/problem+json. See errors.
  • /v1 only changes additively. See the changelog and deprecation policy.