Live marketplace capture

Ticket Scraping API

Capture live inventory, pricing, availability, and seat maps across every ticket marketplace with one API.

Every marketplace, one schema
  • 1normalized schema
  • 0browsers to run
  • $0for failed captures
Overview

What is a ticket scraping API?

A ticket scraping API turns a public marketplace event page into structured JSON. Instead of operating browsers, proxies, parsers, retries, and marketplace-specific integrations, you send an event URL and receive the listings that are available when the request runs.

tickets.dev is a real-time ticket scraping API for retrieving live ticket inventory, pricing, fees, sections, rows, quantities, and seat maps from Ticketmaster, StubHub, Vivid Seats, SeatGeek, TickPick, Gametime, Viagogo, and GoTickets.

Live capture vs cached ticket data

Cached ticket feeds return the last stored version of an event, which may predate a price change, a new listing, or a sold quantity. A live capture reads the marketplace when your API request runs and records the result with a capture timestamp.

Use on-demand scraping when freshness matters for inventory monitoring, price alerts, resale analytics, or cross-marketplace comparison. If you need history, store successive snapshots from the real-time ticket price API.

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

Supported marketplaces

Live capture across every ticket marketplace

Send an event URL to its marketplace endpoint. Every capture returns the same normalized listing schema.

Ticketmaster

Capture live Ticketmaster inventory, all-in prices, availability, and seat maps through one structured API.

GET/v1/capture/ticketmaster
Ticketmaster Scraper API

Vivid Seats

Capture Vivid Seats inventory and pricing, normalized into the same response shape as every tickets.dev source.

GET/v1/capture/vividseats
Vivid Seats Scraper API

StubHub

Capture StubHub inventory through the normalized ticket snapshot shared by every tickets.dev marketplace API.

GET/v1/capture/stubhub
StubHub Scraper API

SeatGeek

Capture SeatGeek listings, pricing, and availability through the shared tickets.dev marketplace schema.

GET/v1/capture/seatgeek
SeatGeek Scraper API

TickPick

Capture TickPick resale listings and all-in pricing for sports, concerts, and theatre through one normalized response.

GET/v1/capture/tickpick
TickPick Scraper API

Gametime

Capture last-minute Gametime inventory and all-in prices across sports, concerts, and theatre in the shared schema.

GET/v1/capture/gametime
Gametime Scraper API

Viagogo

Capture international Viagogo concert, sports, and theatre inventory through the same normalized ticket snapshot.

GET/v1/capture/viagogo
Viagogo Scraper API

GoTickets

Capture GoTickets resale listings, all-in prices, and value scores through the shared tickets.dev ticket snapshot.

GET/v1/capture/gotickets
GoTickets Scraper API

Paciolan

Capture Paciolan box-office inventory: primary seats, published prices, named rows and seats, and the venue's section and seat maps.

GET/v1/capture/paciolan
Paciolan Scraper API
Structured JSON

What fields does the ticket scraper API return?

Each capture returns event and venue details plus listing-level resale marketplace data in a normalized schema. The same field names work across every supported source.

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
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
  ]
}
Built for production

Why use an API instead of maintaining ticket scrapers?

A managed ticket marketplace scraper lets your team build on the data instead of maintaining the capture infrastructure behind it.

Live capture, not a stale cache

Each request captures the event on demand, so prices and availability reflect the marketplace at request time.

One normalized API

Use one key and one response shape instead of building and maintaining a separate ticket scraper for every marketplace.

Scraping infrastructure included

Browser sessions, network routing, page changes, retries, and normalized output are handled as part of each capture.

Failures are not billed

Pricing is based on completed captures, so failed marketplace requests do not consume your paid allowance.

Use cases

Ticket scraping API use cases

Ticket price monitoring

Capture an event on a schedule and record listing, fee, and all-in price changes over time.

Ticket resale analytics

Measure listing depth, available quantities, get-in price, median price, and market movement.

Cross-marketplace comparison

Normalize Ticketmaster, StubHub, Vivid Seats, SeatGeek, TickPick, Gametime, Viagogo, and GoTickets into one comparable dataset.

Inventory alerts

Detect new listings, disappearing inventory, section changes, price drops, and quantity changes.

FAQ

Ticket Scraping API questions

Is there an API for scraping Ticketmaster ticket inventory?

Yes. Send a public Ticketmaster event URL to the Ticketmaster scraper API to receive its current listing-level inventory, pricing, fees, availability, quantities, sections, rows, and optional seat maps as normalized JSON.

How can I get live StubHub ticket listings through an API?

Send the public StubHub event URL to the StubHub capture endpoint. tickets.dev runs the live capture and returns current listings with sections, rows, quantities, ticket prices, fees, and all-in totals.

What is the difference between a ticket API and a ticket scraping API?

A general ticket API may return event metadata, schedules, or a lowest advertised price. A ticket scraping API captures a marketplace event page and returns its current listing-level inventory, pricing, fees, quantities, sections, and rows.

Does tickets.dev return live or cached inventory?

tickets.dev runs an on-demand live capture for each request. It does not return a listing row from a scheduled or stale cache.

Can I use tickets.dev instead of maintaining my own ticket scrapers?

Yes. You send a supported public event URL and receive normalized JSON while tickets.dev operates the marketplace-specific browser and capture infrastructure.

Can I retrieve ticket sections, rows, and quantities?

Yes. Listings include section, row, available quantity, ticket price, fee, all-in total, inventory type, and other marketplace fields when available.

Can I compare StubHub, SeatGeek, and Vivid Seats prices?

Yes. Capture the corresponding event on each marketplace and compare the normalized ticket price, fee, total price, section, row, and quantity fields.

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.