There is no single ticket price. Depending on the source, ticket pricing data can mean the asking price of a resale listing right now, the all-in price a buyer pays, a primary face value, what a ticket actually sold for last week, or the price brokers charge each other on an exchange. They come from different places, and a source that is right for one is usually wrong for another.
This guide separates the kinds of data, shows what they look like on one real event, and maps them to the four kinds of source that supply them. Tickets.dev is one of those sources, a live marketplace data API, and we say where it fits and where it doesn't.
Eight kinds of pricing data
Before comparing providers, decide which of these you need. Each one answers a different question, so start from yours.
| Data | What it is | What it can't tell you |
|---|---|---|
| Current listings | Each group of tickets on sale on a marketplace right now: section, row, quantity, asking price | Whether a listing will sell, or at what price |
| Displayed price | The number a buyer sees first on a listing. Depending on the marketplace and country it's the base price or an all-in price | Whether fees are included, unless the source says so |
| All-in price and fees | The total a buyer pays, with the ticket price and fee that make it up, so listings compare like for like | The fee split, when a marketplace shows only one figure |
| Quantities and depth | How many tickets each listing has, how it can be split, and how many listings and tickets an event has in total | Demand. Supply going down can mean sales or delistings |
| Historical snapshots | Live captures you schedule and store, each timestamped: a price and inventory history built for your events, marketplaces and cadence | What changed between two captures, so capture as often as the question needs |
| Observed sales | What tickets sold for and when, as reported or inferred by whoever collects it | What is on sale now |
| Primary inventory | Seats sold by the box office or primary ticketer at a published price, often with exact seat numbers | Resale supply or prices for the same event |
| B2B / wholesale inventory | Tickets you can buy, sell or distribute through an exchange or a partner integration, with delivery and guarantee terms | What the public marketplaces show buyers |
Displayed vs all-in
A displayed price is only comparable once you know what it includes. Ticketmaster turned on all-in pricing for US events when the FTC's fee rule took effect on May 12, 2025, but marketplaces still differ in what they show and what they break out. In the captures below, Ticketmaster, SeatGeek, Vivid Seats, Gametime and GoTickets showed the fee as a separate charge on every listing; StubHub, TickPick and Viagogo showed one all-in figure with the fee included.
Fees are not a rounding error. In this guide's captures they added between 11% and 36% to the ticket price, so the same listings can rank differently depending on whether you compare base prices or totals. For any comparison, store the ticket price, the fee and the total separately. A fee of zero usually means the fee is included in the price, not that there isn't one.
Listings vs sales
Marketplaces show what is for sale, not what sold. When a listing disappears between two snapshots it may have sold, been delisted, been repriced into a new listing, or been split and partly sold. Only the marketplace and the seller know which.
Sold data from a third party is therefore either reported by a party to the sale (for example, resellers' own point-of-sale data) or inferred from listing changes. Both are useful. They are not the same measurement, so ask any provider which one you are getting.
Retail vs wholesale
The listings fans see are not inventory a business can buy. A listing on a public event page can only be bought there, by a buyer, through that marketplace's checkout. Inventory you can act on as a business, by buying it wholesale, listing it elsewhere or selling it into your own channel, comes through an exchange or a partner agreement, with its own pricing, fulfillment and guarantee terms.
One show, eight sources
The same show on eight marketplaces: Eagles Live at Sphere, Las Vegas, December 11, 2026, captured on each marketplace within about seven minutes of each other on September 22, 2026. Prices are all-in totals.
| Marketplace | Inventory | Listings | Tickets | Cheapest | Median | Fee shown separately |
|---|---|---|---|---|---|---|
| SeatGeek | resale | 1,251 | 4,951 | $402 | $704 | Yes |
| TickPick | resale | 901 | 3,465 | $395 | $681 | No |
| Vivid Seats | resale | 813 | 3,645 | $415 | $708 | Yes |
| Viagogo | resale | 398 | 1,572 | $379.55 | $651.01 | No |
| StubHub | resale | 358 | 1,381 | $442.35 | $764.07 | No |
| Gametime | resale | 348 | 1,616 | $381 | $747.50 | Yes |
| GoTickets | resale | 260 | 1,101 | $436 | $723 | Yes |
| Ticketmaster | primary | 82 | 442 | $303.08 | $740.45 | Yes |
- $303.08 to $442.35 cheapest ticket, depending on the marketplace
- $651.01 to $764.07 median listing
- 82 to 1,251 listings for one show
Three things in this table matter more than the numbers themselves.
- "The price" of the event depends on the source. The cheapest ticket ranged from $303.08 to $442.35. A single price for an event, like a lowest-price field, is one marketplace's number at one moment.
- Primary and resale are different markets. Ticketmaster's 82 listings in this capture were all primary, with a published ticket price and fee ($243.50 + $59.58). Every other marketplace here was resale.
- The same row can carry different prices. The cheapest listing on Vivid Seats, Gametime and TickPick was in the same section and row (110, row 29), at $415, $381 and $395 all-in. Seat numbers weren't published, so we can't say they were the same tickets. Resellers often list one set of tickets on several marketplaces, and each marketplace adds its own fee.
Tracking this over time is a separate job; the price tracking guide walks through it on another event.
Where the data comes from
- Official APIsEvent catalogs; ticket-level data for partners
- Live data APIsWhat a buyer sees on the page, now
- Historical datasetsPrice history and sold data
- B2B inventoryTickets you can buy, sell or distribute
Official ticketing APIs
The ticketing companies' public APIs are built for event discovery and selling through partners, not for pricing data. They are the right source for what is on, where and when, and they come with terms of use that limit what you can build.
- Ticketmaster. The public Discovery API is free and returns events, venues and performers. Ticketmaster removed price ranges from its Discovery Feed in March 2025, and in October 2026 almost none of the events the API returned carried one. Its ticket-level APIs are not open: Inventory Status is limited to authorized clients, and the Partner API and Top Picks to Ticketmaster's distribution partners. Our Ticketmaster Discovery API guide tests each of these.
- SeatGeek. The Platform API needs a registered client: a request without one is refused with "Client is required". It reports price statistics per event, a summary of the market rather than the listings behind it.
- StubHub. StubHub's API is built for sellers managing their own listings, not for reading the listings buyers see.
What none of the public APIs return is the listing-level view: every listing on an event with its section, row, quantity, ticket price and fee.
Live marketplace data APIs
A live marketplace data API reads a public event page when you call it and returns what a buyer would see at that moment, as structured data. This is the only source of current, listing-level prices across marketplaces that don't offer them through an official API. Providers range from per-site scrapers you run yourself to managed APIs; the differences are coverage, reliability, whether responses share a schema, and whether data is captured on request or served from a cache.
Tickets.dev is a live marketplace data API. Each call captures one event on one marketplace and returns every listing with its section, row, quantity, ticket price, fee and all-in total, plus event and venue details and, on request, hosted section and seat maps where the marketplace draws them. The response schema is the same on every supported marketplace, captures are live rather than cached, and a failed capture isn't billed. How the capture side works is covered on the ticket scraping API page, and the fields on the ticket price API and ticket inventory API pages.
A capture is one moment, and that makes it a building block. Schedule captures and store them, and you have your own price and inventory history, covering exactly the events, marketplaces and frequency you choose, with a timestamp on every record; listings that disappear between captures are the raw material for inferred sales. What a capture can't do is see reported sales or act on the inventory it reads. And it runs a real page load, which takes seconds rather than milliseconds.
Historical and analytics datasets
Historical and analytics providers sell accumulated data: price history, sold data and the analysis built on them. Their advantage is time: they can answer what a section cleared at for last year's tour, because they were collecting before you started.
The other way to get a dataset is to build it. Schedule live captures of the events and marketplaces you care about and store every one: you get raw, listing-level rows, timestamped, at the frequency your question needs, with no gaps in coverage you didn't choose. It starts on the day you start, so many teams use both: a bought dataset for the past and their own captures from now on.
- Victory Live includes a Data + Insights product with market data and historical sales alongside its broker tools.
- Stage Front's Broker Suite adds sold data back to 2021 to its consignment platform.
These are research products first. Check how fresh the "current" data is, how sales are measured, and whether you can export raw rows or only see dashboards. Our reseller software guide covers them in more detail.
B2B and wholesale inventory
Broker exchanges and partner integrations deal in inventory you can act on. Victory Live's Industry Marketplace (formerly the Ticket Evolution exchange) and TicketNetwork's Mercury are broker-to-broker exchanges; Mercury guarantees purchases up to 200% or replacement with equivalent tickets. Ticketmaster's Partner API covers availability, fees, holds and purchases for companies with an official distribution deal.
These sources answer "can I buy or sell this, and on what terms", not "what is the public market asking". Where the same tickets are listed on both, the business price is usually lower: it is the seller's wholesale price, before the markup and buyer fees a public page adds. Some marketplaces run a wholesale channel of their own alongside the public site. Access comes with a business relationship, even when it is an API.
Comparison
What each kind of source typically supplies. Individual providers vary, so treat this as the question list, not the answer.
| Source type | Live listings | Current prices | Inventory | Historical data | Observed sales | Buy as a business | Multi-marketplace | Typical use |
|---|---|---|---|---|---|---|---|---|
| Official ticketing APIs | Partners only | Event-level publicly; more for partners | Partners only | No | No | Partners only | No, one company | Event catalogs, discovery, affiliate apps |
| Live marketplace data APIs | Yes | Per listing, with fees where shown | As shown to buyers | Yours, built from scheduled captures | Inferred from your own captures | No | Depends on provider | Monitoring, pricing inputs, ticket apps |
| Historical and analytics datasets | Sometimes | Varies in freshness | Varies | Yes | Yes; method varies | No | Usually | Research, pricing strategy, backtesting |
| B2B exchanges and partner APIs | The exchange's own | The exchange's own | The exchange's own | Sometimes | Your own sales | Yes | Through distribution | Broker operations, distribution |
Choosing a source
Start from the job, then pick the data, then the source.
| Job | Data you need | Source type |
|---|---|---|
| Price monitoring | Current listings with all-in prices, captured on a schedule | Live marketplace data API |
| Inventory monitoring | Listing and ticket counts, quantities, sections | Live marketplace data API |
| Dynamic pricing inputs | Current competing listings, plus history if your model uses it | Live data API, optionally with a historical dataset |
| Historical research | Long price history and sold data | Historical dataset for past seasons, your own captures from now on |
| Broker operations | Your inventory, distribution, fulfillment and sales | POS and B2B exchanges, plus market data for pricing |
| Ticket applications | Events to show, then live listings and seat maps | Official API or event catalog, plus a live data API |
| Market research | Coverage across marketplaces, history, sometimes sales | Your own dataset from a live data API, or a historical dataset |
| AI and agent applications | Structured, current data an agent can call for one event at a time | Event catalog to find the event, live data API to price it |
A live data API also changes whose data it is. A packaged dataset is the same one your competitors can buy, collected on someone else's schedule. Captures you run yourself cover the events, marketplaces and moments you care about, at the frequency your strategy needs, and the dataset they build is yours alone. Over time that becomes an edge a bought dataset can't give you.
Most real systems combine two. A pricing tool for resellers might use a historical dataset to set expectations and live captures to price against the market today. A consumer app might use an official catalog for events and a live data API for what is on sale.
Questions to ask a provider
Whatever the source, these questions separate the kinds of data quickly:
- Is it live or cached? If cached, how old can a price be, and is the capture time on every record?
- Which price is it? Base, displayed or all-in, and is the fee a separate field?
- Listings or summaries? Every listing with section, row and quantity, or a lowest price and a count?
- Primary, resale or both? And is that labeled per listing?
- How is a sale defined? Reported by a party to it, or inferred from a listing disappearing?
- Which marketplaces, and in one schema? Five sources in five shapes is five integrations.
- What may you do with the data? Official APIs restrict caching, resale and competing products; check every source's terms.
For Tickets.dev's own answers, field by field, see the API reference.