Ticket market data, primary and secondary, from one API

Every listing for an event on the primary market and on resale, with prices, fees, sections, rows and quantities, captured when you ask and returned in one schema.

Get API keyRead the docs

18 marketplaces, one schema. Failed captures are never billed.

12,906 tickets on saleEagles at Sphere, Dec 11, 7 marketplaces
Primary, Ticketmaster
161
Resale, 6 marketplaces
12,745
Live captureEvery listing, primary and resale, in one response
Overview

What is ticket market data?

Ticket market data is what is on sale for a live event and at what price: the primary inventory a box office still has, the resale listings sellers have posted, and the prices, fees and quantities behind each. Read across marketplaces and over time, it shows how big the market for an event is, where it prices and how fast supply is moving.

Tickets.dev captures it from the source. One capture reads one event on one marketplace and returns every listing on it, marked primary or resale. Ticketmaster and the box offices (Paciolan, ProVenue, GoFevo, Telecharge, Broadway Direct, ATG Tickets, Cirque du Soleil, Vegas.com, and Spotlight.Vegas) give the primary side, and every resale marketplace gives the other, with the same field names on both.

On October 18, 2026, we captured one Eagles at Sphere date (December 11) on seven marketplaces within about a minute. Ticketmaster had 52 primary listings for 161 tickets, with a get-in price of $303.08 all-in. Six resale marketplaces had 3,189 listings for 12,745 tickets, and the cheapest resale ticket was $385 on TickPick.

Start with the API documentation, review the complete ticket marketplace API, or try a marketplace endpoint in the playground.

Supported marketplaces

Primary and resale marketplaces, one schema

Capture the box office and every resale marketplace for the same event. Each returns the same listing fields, marked primary or resale.

Ticketmaster market dataStubHub market dataStubHub International market dataSeatGeek market dataTickPick market dataVivid Seats market dataGametime market dataViagogo market dataGoTickets market dataPaciolan market dataProVenue market dataGoFevo market dataTelecharge market dataBroadway Direct market dataATG Tickets market dataCirque du Soleil market dataVegas.com market dataSpotlight.Vegas market data
Structured JSON

What ticket market data each capture returns

One capture is one event on one marketplace, in full: the event and venue, market statistics computed from every listing, and the listings themselves with inventoryType telling primary from resale.

Event and performers

Which event was captured: marketplace IDs, names, performers, dates in local and UTC time, and the source page URL.

sourceeventIdeventNameperformerseventDateLocaleventDateUtcsourceUrlnote

Venue

The venue behind the event, down to street address, state, and timezone.

venueIdvenueNamevenueAddressvenueCityvenueStatevenueTimezone

Capture context and seat maps

When the snapshot ran, its currency, and hosted section-level and seat-level maps for the venue.

capturedAtcurrencysectionLevelUrlseatLevelUrl

Market statistics

Listing depth and price distribution computed from the full captured listing set, not a sample.

listingCountticketCountgetInPricemedianPriceavgPricemaxPrice

Every listing, itemized

All current listings with seat location, quantities, price components, ticket type, seats, and marketplace notes.

listingIdinventoryTypesectionrowquantityticketPricefeetotalPriceticketTypesellableQuantitiesgroupseatslistingNotesdealScore

Venue layout

With maps on, the venue map as data: every section, row, and seat, with capacities at seat level.

venueLayoutlevelcapacitysectionsrowsseats
Example capture response
{
  "source": "ticketmaster",
  "eventId": "17006483D6FAFC60",
  "eventName": "Eagles Live at Sphere",
  "performers": [
    {
      "performerId": "734977",
      "name": "Eagles",
      "master": true
    }
  ],
  "venueId": "189524",
  "venueName": "Sphere",
  "venueAddress": "255 Sands Avenue",
  "venueCity": "Las Vegas",
  "venueState": "NV",
  "venueTimezone": "America/Los_Angeles",
  "eventDateLocal": "2026-12-11T20:30:00-08:00",
  "eventDateUtc": "2026-12-12T04:30:00+00:00",
  "sourceUrl": "https://www.ticketmaster.com/…",
  "capturedAt": "2026-08-01T22:05:48Z",
  "currency": "USD",
  "note": "PLEASE NOTE: Pricing is all-in and…",
  "sectionLevelUrl": "https://storage.tickets.dev/…",
  "seatLevelUrl": "https://storage.tickets.dev/…",
  "stats": {
    "listingCount": 136,
    "ticketCount": 1037,
    "getInPrice": 303.08,
    "medianPrice": 710.95,
    "avgPrice": 746.14,
    "maxPrice": 2309.85
  },
  "listings": [
    {
      "inventoryType": "primary",
      "section": "101",
      "row": "34",
      "quantity": 2,
      "ticketPrice": 243.5,
      "fee": 59.58,
      "totalPrice": 303.08,
      "ticketType": "limited view of sphere screen…",
      "sellableQuantities": "1,2",
      "seats": "1,2"
    },
      ⋯ 135 more listings
  ],
  "venueLayout": {
    "level": "seat",
    "capacity": 16390,
    "sections": [
      ⋯ 44 sections
    ]
  }
}
Built for production

Market data you can audit

Every number traces back to a listing, a marketplace and a capture time, so you can check it rather than trust an index.

Primary and resale in one schema

inventoryType marks each listing primary or resale, so face-value inventory and resale asks sit in the same table without a second parser.

Every listing, not a summary

Listing count, ticket count, get-in and median price come with the listings they were computed from.

Live at request time

Each capture reads the marketplace when you call it and stamps capturedAt, so the data is as fresh as your schedule.

Your series, your cadence

Store each capture and the time series is yours: hourly before an on-sale, daily across a residency, whatever the question needs.

Use cases

Ticket market data use cases

Market size per event

Add up listings and tickets across every marketplace that sells a show, primary and resale.

Primary vs resale spread

Set box-office prices beside resale asks for the same event, section by section.

Inventory drawdown

Track how many tickets stay on sale as the date approaches. Fewer listings can mean sales, delistings or price moves, so treat it as supply, not sales.

Cross-marketplace coverage

See which marketplaces carry an event and how deep each one is, starting from the free event catalog.

Research datasets

Build panels of venues, tours or leagues from timestamped captures you control.

Pricing inputs

Feed current asks and depth into pricing rules, models and alerts.

Guides

Build it step by step

Walkthroughs for building the use cases above.

How to Track Ticket Prices Across Multiple Marketplaces

Capture every marketplace on a schedule and keep each snapshot as price and inventory history.

Compare Ticket Prices Across Marketplaces with One API

Compare the same seats across marketplaces, using the Eagles at Sphere captures behind the example above.

Live Ticket Pricing Data: APIs, Providers & Data Sources

What displayed, all-in, sold and wholesale prices mean, and which sources supply each.

How to Track Sphere Las Vegas Ticket Prices and Inventory

One venue's market end to end: who sells Sphere, how primary and resale move, and what collecting it costs.

FAQ

Ticket Market Data questions

What is ticket market data?

The listings, prices, fees and quantities on sale for a live event, on the primary market and on resale. Captured over time, it shows how much is on sale, at what price, and how that changes.

Is there a ticket market data API?

Yes. GET /v1/capture with a public event page URL returns that event's market on that marketplace as JSON: every listing with section, row, quantity, ticket price, fee and all-in total, plus listing count, ticket count, get-in and median price.

Does Tickets.dev have primary and secondary ticket data?

Yes. Ticketmaster and the box offices (Paciolan, ProVenue, GoFevo, Telecharge, Broadway Direct, ATG Tickets, Cirque du Soleil, Vegas.com, and Spotlight.Vegas) return primary inventory at the published price, and every resale marketplace returns resale listings. Each listing carries inventoryType, so the two never mix by accident.

Does Tickets.dev report completed ticket sales?

No. A capture shows what is on sale. When a listing disappears between two captures it may have sold, been delisted or been relisted at a new price, and the captures can't tell which. Measure supply on sale over time and keep that caveat with the numbers.

Does Tickets.dev sell historical ticket data?

No. Captures are live, so history starts the day you start capturing an event. Store each snapshot and you own the series at the cadence you chose.

How do I cover the whole market for one event?

Find the event on every marketplace with the free event catalog (GET /v1/events), then capture each marketplace's URL. One capture covers one event on one marketplace, so a show on seven marketplaces is seven captures.

Start free

Run your first capture free

Send any supported event URL and get live listings, all-in prices, and seat maps back as normalized JSON. No credit card required.

Get API keyTry the playground