tickets.dev

Ticketmaster Scraper API

Capture live Ticketmaster ticket inventory through a scraping API. Send a public Ticketmaster event URL and receive current listings, pricing, fees, availability, and seat maps as structured JSON.

The API endpoint is https://api.tickets.dev/v1/capture/ticketmaster

Ticketmaster scraper API for live inventory

Each request captures current listing-level inventory with sections, rows, quantities, prices, fees, and optional seat maps in the same normalized JSON used across every marketplace.

0% Progress
Loading example…
JSON response
{
  "status": "Loading example…"}

Capture a Ticketmaster event

Submit a public event page URL. The request runs the capture and returns one normalized snapshot when it completes.

MethodEndpoint
GET/v1/capture/ticketmaster
Code to integrate
import requests

endpoint = "https://api.tickets.dev/v1/capture/ticketmaster"
response = requests.get(
    endpoint,
    params={"eventUrl": event_url},
    headers={"x-api-key": api_key},
)
snapshot = response.json()

Query parameters

ParameterTypeDescription
eventUrlstring
required
A public Ticketmaster event page URL to capture, from ticketmaster.com or livenation.com. Any country domain or subdomain of those works as well. The match is on the marketplace name, not the exact host. An event URL from a different marketplace returns 400 marketplace_mismatch.
includeVenueMapsboolean
optional
Render the venue maps for this capture and host them, filling sectionLevelUrl and seatLevelUrl. Off by default, because the maps add render and upload time to a request most callers make for pricing alone, so both fields come back as empty strings unless you pass true.
apiKeystring
optional
Your API key, when you send it in the query string rather than the x-api-key header. Either is accepted, and the key is required one way or the other. Keep it server-side. It carries your full quota. The public sandbox key tk_test_sandbox hits the same URL and returns fixture snapshots without spending a capture.

Example response

One capture of a real Ticketmaster event, trimmed to two listings. Every marketplace returns this same shape, so a parser written once works against all of them.

{
  "source": "ticketmaster",
  "eventId": "17006483D6FAFC60",
  "eventName": "Eagles Live at Sphere",
  "performers": [
    {
      "performerId": "734977",
      "name": "Eagles",
      "master": true
    },
    {
      "performerId": "3164219",
      "name": "Eagles Live at Sphere",
      "master": false
    }
  ],
  "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/eagles-live-at-sphere-las-vegas-nevada-12-11-2026/event/17006483D6FAFC60",
  "capturedAt": "2026-08-01T22:05:48.262458+00:00",
  "currency": "USD",
  "note": "PLEASE NOTE: Pricing is all-in and includes fees (before taxes if applicable). This event may include immersive elements such as seat haptics, movement sensations, flashing lights, intense lighting, visual effects, loud noises, and atmospheric simulations. Such elements may aggravate certain medical or physical conditions, and guests should take into consideration these elements, including if they have a history of discomfort or physical symptoms when experiencing them. Visit the Sphere FAQs on thespherevegas.com closer to your event date for the newest event information.",
  "seatLevelUrl": "https://storage.tickets.dev/seatmaps/ticketmaster/seat/17006483D6FAFC60/1785621947.svg",
  "sectionLevelUrl": "https://storage.tickets.dev/seatmaps/ticketmaster/section/17006483D6FAFC60/1785621946.svg",
  "stats": {
    "listingCount": 136,
    "ticketCount": 1037,
    "getInPrice": 303.08,
    "medianPrice": 710.95,
    "avgPrice": 746.14,
    "maxPrice": 2309.85
  },
  "listings": [
    {
      "listingId": "",
      "inventoryType": "primary",
      "section": "101",
      "row": "34",
      "quantity": 2,
      "ticketPrice": 243.5,
      "fee": 59.58,
      "totalPrice": 303.08,
      "ticketType": "limited view of sphere screen - full view of band and stage limited view of sphere screen - full view of band and stage main level seating limited view of sphere screen - full view of band and stage accessible mobility",
      "sellableQuantities": "1,2",
      "group": "",
      "seats": "1,2",
      "listingNotes": "",
      "dealScore": ""
    },
    {
      "listingId": "",
      "inventoryType": "primary",
      "section": "101",
      "row": "35",
      "quantity": 2,
      "ticketPrice": 243.5,
      "fee": 59.58,
      "totalPrice": 303.08,
      "ticketType": "limited view of sphere screen - full view of band and stage limited view of sphere screen - full view of band and stage main level seating limited view of sphere screen - full view of band and stage accessible mobility",
      "sellableQuantities": "1,2",
      "group": "",
      "seats": "1,2",
      "listingNotes": "",
      "dealScore": ""
    }
    // …134 more listings
  ]
}

Real-time Ticketmaster pricing and availability

Store successive captures to monitor new and removed listings, price changes, fee changes, quantity movement, and inventory depth over time. The ticket price API guide covers all-in comparison, price alerts, resale analytics, and dynamic pricing workflows.

Ticketmaster API questions

What does the Ticketmaster API return?

One normalized snapshot of the event as it looks right now: every listing with its section, row, quantity, ticket price, fee and all-in total, plus event and venue details. Ask for venue maps and the same response carries hosted section and seat level map images tied to those listings.

Why use a Ticketmaster scraper instead of the official API?

Catalog and partner APIs often focus on events, performers, or seller workflows. tickets.dev captures the inventory visible on a public event page, including current listings, buyer-facing prices, fees, quantities, locations, and availability. It also removes the browser fleet, parsers, network routing, retries, and marketplace page maintenance involved in operating a production scraper.

Which Ticketmaster URLs does it accept?

Any public event page URL from ticketmaster.com and livenation.com. Country domains and subdomains work as well. The match is on the marketplace, not the exact host.

Is the Ticketmaster data live or cached?

Live. Each call opens the event page and reads its current listings and prices. There is no crawl schedule to wait on and no cached row to go stale.

Does Ticketmaster use the same response shape as the other marketplaces?

Yes. Every tickets.dev marketplace API returns the identical snapshot schema, so a parser written against Ticketmaster works unchanged against Vivid Seats, StubHub, SeatGeek, TickPick, Gametime, Viagogo, GoTickets and Paciolan.

How is the Ticketmaster API priced?

Per completed capture, starting at $0.050 each on the Starter plan. Failed requests are never charged, and every plan includes every marketplace and live seat maps.

Other marketplace APIs

The same endpoint shape and the same response schema cover every marketplace we support: Vivid Seats API, StubHub API, SeatGeek API, TickPick API, Gametime API, Viagogo API, GoTickets API, and Paciolan API. Start with the ticket scraping API, explore live ticket inventory and real-time ticket pricing, see every ticket marketplace API, check per-capture pricing, or talk to us about volume.