API reference

Introduction

The Tickets.dev API scrapes live marketplace inventory on demand. There is no crawl to schedule and no cache to go stale: each call opens the event, reads its current listings and prices, and returns the result to you. Ask for the seat maps and it renders those too.

Learn the product concepts in the ticket scraping API, ticket inventory API, ticket price API, seat map API, and ticket events API guides.

All endpoints live under a single base URL and speak JSON.

https://api.tickets.dev/v1

Authentication

Every request must carry your API key. Send it in the x-api-key header. Create a key from the account page.

curl -G https://api.tickets.dev/v1/capture/ticketmaster \
  --data-urlencode "url=$EVENT_URL" \
  -H "x-api-key: $TICKETS_DEV_KEY"

An apiKeyquery parameter is accepted as well, for callers that can't set a header.

Sandbox

There is no separate sandbox host. Same base URL, same paths, same query parameters, same snapshot shape. One public key returns fixtures instead of a live capture.

tk_test_sandbox

Build against that key. Cut over by swapping it for your org's tk_live_… key. Nothing else in the request should have to change: not the URL, not the query, not the parser.

curl -G https://api.tickets.dev/v1/capture/ticketmaster \
  --data-urlencode "url=https://www.ticketmaster.com/event/example" \
  -H "x-api-key: tk_test_sandbox"

Validation still runs, so a bad request fails the same way it would in production. Responses carry the header Tickets-Sandbox: true. Streaming captures send the same progress events, then the snapshot.

Quickstart

Point the API at any supported event URL. The request runs the capture and returns the whole event: every listing on it, with prices and fees, in one response.

curl -G https://api.tickets.dev/v1/capture/ticketmaster \
  --data-urlencode "url=https://www.ticketmaster.com/event/XXXXXXXX" \
  -H "x-api-key: $TICKETS_DEV_KEY"

Endpoints

Pass an event URL and every marketplace returns the identical snapshotobject. The marketplace is optional: it comes from the URL's host unless you name it with source= or in the path.

Parameters

Ticket events

/v1/events is the free ticket event discovery and matching API: event name, venue, date, performers, and a sources array of marketplace ids and URLs. Search by name, or pass a marketplace URL to resolve one unified event. It never returns prices, listing counts, or ticket counts. Those stay on capture. See the ticket events API.

One parameter does the searching. ?query= takes a name, a venue or performer, a slug, or any marketplace URL, with or without a scheme, and works out which it is. An event page returns that event; a venue or performer page returns the upcoming dates. Narrow with ?from= / ?to= and ?source=. Native event ids use ?source=ticketmaster&eventId=; ?eventId= also takes the catalog id. To capture listings and prices, take a sources[].url from the response and pass it to /v1/capture?url=.

The catalog is mapped from Ticketmaster, StubHub, SeatGeek, TickPick, Vivid Seats, Gametime, GoTickets, and Paciolan today, with Viagogo, ATG Tickets, ProVenue, and GoFevo rolling out next. Until one lands, /v1/events answers source_not_indexed for it.

Responses carry page, pageSize, total, numberOfPages and hasMore above the events array.

Searches return upcoming events. Ones that have already started are left out unless from says otherwise; events with no start time published are always included, since there is nothing to compare. Exact lookups by eventId or by URL are never filtered by date.

Catalog reads require a key, are never billed, and are not rate limited.

curl -G https://api.tickets.dev/v1/events \
  --data-urlencode "query=eagles sphere" \
  --data-urlencode "from=2026-12-01" \
  -H "x-api-key: $TICKETS_DEV_KEY"

{
  "page": 1,
  "pageSize": 20,
  "total": 1,
  "numberOfPages": 1,
  "hasMore": false,
  "events": [
    {
      "id": "01M0FVJHZRFPS6Y3XM5M0BQ1RH",
      "name": "The Eagles",
      "eventDateLocal": "2026-12-11T20:30:00-08:00",
      "eventDateUtc": "2026-12-12T04:30:00.000Z",
      "venue": {
        "name": "Sphere at The Venetian Resort",
        "city": "Las Vegas",
        "state": "NV",
        "country": "US",
        "timezone": "America/Los_Angeles"
      },
      "performers": [{ "performerId": "44705", "name": "The Eagles", "master": true }],
      "sources": [
        {
          "marketplace": "ticketmaster",
          "eventId": "17006483D6FAFC60",
          "url": "https://www.ticketmaster.com/eagles-live-at-sphere-las-vegas-nevada-12-11-2026/event/17006483D6FAFC60"
        },
        {
          "marketplace": "vividseats",
          "eventId": "7256971",
          "url": "https://www.vividseats.com/the-eagles-tickets-las-vegas-sphere-at-the-venetian-resort-12-11-2026--concerts-adult-contemporary/production/7256971"
        },
        {
          "marketplace": "stubhub",
          "eventId": "161551904",
          "url": "https://www.stubhub.com/the-eagles-las-vegas-tickets-12-11-2026/event/161551904"
        },
        {
          "marketplace": "gotickets",
          "eventId": "1794730",
          "url": "https://gotickets.com/tickets/1794730/the-eagles-tickets/msg-sphere-las-vegas-nv-12-11-2026"
        }
      ],
      "updatedAt": "2026-08-25T09:14:02.418Z"
    }
  ]
}

Take any sources[].url from the response and pass it to /v1/capture?url=to get that marketplace's live listings and prices.

The snapshot object

Every capture returns one snapshot: the full listing payload for one event. It carries the event metadata, the currency, the derived stats, the flat list of listings, URLs to the rendered seat maps, and the venue layout.

{
  "source": "ticketmaster",
  "eventId": "17006483D6FAFC60",
  "eventName": "Eagles Live at Sphere",
  "venueId": "189524",
  "venueName": "Sphere",
  "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",
  "currency": "USD",
  "sectionLevelUrl": "https://storage.tickets.dev/…/section.svg",
  "seatLevelUrl": "https://storage.tickets.dev/…/seats.svg",
  "stats": {
    "listingCount": 136,
    "ticketCount": 1037,
    "getInPrice": 303.08,
    "medianPrice": 710.95,
    "avgPrice": 746.14,
    "maxPrice": 2309.85
  },
  "listings": [{
    "listingId": "",
    "inventoryType": "primary",
    "section": "208",
    "row": "9",
    "quantity": 3,
    "ticketPrice": 1157.5,
    "fee": 208.35,
    "totalPrice": 1365.85,
    "sellableQuantities": "1,2,3"
  }],
  "venueLayout": {
    "level": "seat",
    "capacity": 16390,
    "sections": [{
      "section": "101",
      "group": "",
      "ga": false,
      "capacity": 522,
      "rows": [{ "row": "34", "capacity": 21, "seats": "1,2,3,…,19,20,21" }]
    }]
  }
}

The stats object

stats is worked out from the listings. Every figure is per ticket and all-in, like totalPrice, and counted per listing: a ten-seat listing counts once. A capture with no listings reports zeroes.

The listing object

Each entry in listings is one group of same-price seats. Every field below comes back from every marketplace.

Seat maps

Pass includeVenueMaps=true and the capture renders two SVGs and hosts them for you:

• sectionLevelUrl, the overview: the venue outline, the stage, and one shape per section.
• seatLevelUrl, the zoomed detail: rows or seats, as fine as the venue's map goes.

The two share a viewBox. The seat file is one group in the section map's coordinates, so append it to the same <svg> when someone zooms in. Sections are tens of kilobytes and seats hundreds, so fetch it only on zoom.

Every region carries data-section, and data-row where the map has rows, spelled the way listings[].section spells it, so a listing binds to its shape by name.

The same parameter fills venueLayout: the sections, rows and seats behind those shapes as data.

Without the parameter both fields come back as empty strings. The fields are always present, so a client never has to branch on their existence. seatLevelUrl is also empty where the marketplace publishes only a section level map.

curl -G https://api.tickets.dev/v1/capture/ticketmaster \
  --data-urlencode "url=$EVENT_URL" \
  --data-urlencode "includeVenueMaps=true" \
  -H "x-api-key: $TICKETS_DEV_KEY"

The venueLayout object

venueLayout is the venue map as data: its sections, the rows in each and the seats in each row. It is read from the same map as the seat maps, for this event's setup of the venue. Pass includeVenueMaps=true to get it; without it the field is { "level": "none", "sections": [] }.

Names match. Sections, rows and seats are spelled the same in venueLayout, in listings and in the maps' data-section, data-row and data-seat.

Seats are in order across the row. A row numbered odd on one side of the aisle and even on the other reads 5,3,1,2,4,6, so neighbours sit next to each other in the string.

level is how deep the map goes. Capacities come at seat level, counted from the seats.

Section

Row

{
  "level": "seat",
  "capacity": 16390,
  "sections": [
    {
      "section": "101",
      "group": "",
      "ga": false,
      "capacity": 522,
      "rows": [
        {
          "row": "33",
          "capacity": 21,
          "seats": "1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21"
        },
        {
          "row": "36",
          "capacity": 15,
          "seats": "1,2,3,4,5,6,7,8,9,10,11,12,13,14,15"
        }
      ]
    }
  ]
}

Marketplaces

Every marketplace returns the same snapshot. Pass an event URL from one of its domains and the marketplace is worked out for you. The paths below are the explicit form, and the last segment of each is also the value for source=:

Marketplace	Path	Event URL domains
Ticketmaster API	/v1/capture/ticketmaster	ticketmaster.com, livenation.com
StubHub API	/v1/capture/stubhub	stubhub.com
SeatGeek API	/v1/capture/seatgeek	seatgeek.com
TickPick API	/v1/capture/tickpick	tickpick.com
Vivid Seats API	/v1/capture/vividseats	vividseats.com
Gametime API	/v1/capture/gametime	gametime.co
Viagogo API	/v1/capture/viagogo	viagogo.com
GoTickets API	/v1/capture/gotickets	gotickets.com
Paciolan API	/v1/capture/paciolan	evenue.net
ATG Tickets API	/v1/capture/atg	atgtickets.com, us.atgtickets.com
ProVenue API	/v1/capture/provenue	mlb.tickets.com, mpv.tickets.com
GoFevo API	/v1/capture/gofevo	gofevo.com

A URL from a domain we don't recognize works if you name the marketplace with source=; without it the capture returns marketplace_required. A URL from a different marketplace than the one you named returns marketplace_mismatch.

Errors

Every error carries a stable code and the request_id that also comes back in the x-request-id header. Branch on the code, not the status: several distinct failures share a status, and the code is what tells you whether retrying is worth it.

{
  "error": {
    "code": "marketplace_mismatch",
    "message": "Requested source \"stubhub\" but the URL is a ticketmaster event.",
    "outcome": "rejected",
    "retryable": false,
    "request_id": "6068316c-29d3-447f-b42c-b46f80debd0d"
  }
}

outcome and retryable say what to do with any error, including codes added after you integrate.

Rate limits

Each plan adds captures each invoice and sets a ceiling on how many captures can run at once. Spending them returns 429 quota_exceeded; whatever is left stays on your balance. See the pricing table for the limits on every tier.

Data use

A capture only reads public data: the listings, prices, fees and seat maps the marketplace shows any visitor on its event page, with no login. Tickets.dev puts no license terms on what a capture returns. Store it, analyze it, build products on it and show it to your own users, with no attribution required.