API Reference
Full reference for the SeatData API — endpoints, parameters, and request/response examples.
The SeatData API provides programmatic access to secondary ticket marketplace data - event metadata, pricing time series, sales records, and listings - for integration into analytics and trading workflows.
Getting Started
- Create an account. Register or log in.
- Subscribe to API access on the Pricing page.
- Generate your API key under API Keys in the sidebar.
- Make your first request. See the examples below or the Getting Started guide.
Python developers can install our SDK with pip install seatdata-sdk (README). Other languages call the API directly over HTTP.
Pricing
Only four endpoints consume pulls. Everything else is free (subject to subscription requirements).
| Endpoint | Charge |
|---|---|
GET /v1/events/{event_id}/stats |
1 pull per event. Free when no new data exists, and free for pagination. |
GET /v0.3/salesdata/get (and v0.1, v0.2) |
1 pull per event. |
POST /v0.3/salesdata/batch |
1 pull per event in the batch that returns data. |
GET /v0.1.1/listings/get (and v0.1) |
1 pull per event. Free when listings have not refreshed. |
Two pricing plans are available: a tiered plan (default - details) and a flat-rate plan at $0.015 per request. To switch to flat-rate, open a support ticket.
Versions
- v1 - account info, usage reporting, event search, and event stats.
Uses
Authorization: Bearer <key>auth, Stripe-style envelopes, cursor pagination, ISO-8601 timestamps. - v0.x - current home for sales data, listings, asynchronous event-add,
and the daily CSV download. These do not yet have a v1 equivalent and
remain fully supported. Only the v0.3.1 POST search is superseded - by
GET /v1/events/search.
Both versions share the same auth and the same API keys. New integrations should use v1 for the endpoints it covers and v0.x for everything else.
Authentication
Both v1 and v0.x endpoints accept either of these headers:
Authorization: Bearer <api_key>(preferred - modern convention)api-key: <api_key>(legacy - used by v0.x docs historically)
Either header works against any endpoint. New SDK code should use
Authorization: Bearer.
Rate Limits
Rate limits apply per API key. See the Rate Limits guide for how to discover your current limits and handle 429 responses.