Ticket data API
Ticker API: the ticket market data API.
The readings the app shows, returned to your own code as JSON: an event's current prices and listings, its price history, a search from a name to an id, and performer rank.
What a key returns
- Event readings
- Resale prices, face prices, listings, tickets and demand for one event or a batch of events.
- Price history
- The same readings as a series, for the window you ask for.
- Search
- An event or performer name in, Ticker ids out.
- Performer rank
- Where a performer stands and how that moved over time.
- Views and screens
- The events that match a View you saved in the app, or a question you write in plain language.
Authentication
Every request carries an API key as a bearer token in the Authorization header. Keys start with tk_live_. An account can hold five keys at once, so you can rotate one without downtime, and you create and revoke them in Settings. Ticker stores only a hash of each key.
Reference
- API reference
- findticker.com/docs/api
- OpenAPI document
- openapi-v1.json
- Base URL
- api.findticker.com
Plans with a key
Ultra includes an API key, turned on for your account on request. Plans
Enterprise delivers the data into your own product, on terms agreed by contract.
Questions
- Is there an API for ticket market data?
- Yes. The Ticker API returns primary and resale prices, listings, demand and price history for each event as JSON over HTTPS. The reference is at findticker.com/docs/api.
- How does the Ticker API authenticate?
- With an API key sent as a bearer token in the Authorization header. Keys start with tk_live_, an account can hold five at once, and you create and revoke them in Settings.
- Is there an OpenAPI document?
- Yes. The OpenAPI v1 document is at findticker.com/docs/api/openapi-v1.json, so you can generate a client in the language you use.
- Which plans include an API key?
- Ultra includes an API key, turned on for your account on request. Enterprise delivers the data into your own product, on terms agreed by contract.