Venue maps and seating chart data

Seat Map API

Capture the venue map the marketplace draws for an event, hosted as SVG, with every section, row and seat of the venue as data, joined to the live listings and prices in the same response.

Get API keyRead the docs
Every marketplace, one schema
  • 1normalized schema
  • 0browsers to run
  • $0for failed captures
Overview

What is a seat map API?

A seat map API returns the seating chart for a specific event as data your application can render, not a screenshot. Tickets.dev captures the map the marketplace itself draws for that event, hosts it as SVG, and returns its URLs inside the same snapshot that carries every listing. Section names in the map match the section field on each listing, so a region can be joined to the inventory and prices behind it.

Two maps come back when the marketplace has them. The section level map is the venue overview a fan sees first. The seat level map is the zoomed layer with rows and seats, where the venue's map has one.

Maps are optional on every capture. Pass includeVenueMaps=true and the response fills sectionLevelUrl and seatLevelUrl, plus venueLayout: the venue map as data, every section, row and seat, with capacities at seat level. Leave it off and the capture skips the render, which keeps price-only requests fast.

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

Live examples

Real seat maps, bound to real listings

Every marketplace below is a bundled capture with its maps. Pick a section or a listing and the other side follows. Run any of them again to capture the event as it stands right now.

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

Venue maps from every marketplace

Ask any marketplace endpoint for maps and the capture hosts the section level map, plus the seat level map wherever the marketplace draws one.

Ticketmaster

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

GET/v1/capture/ticketmaster
Ticketmaster Seat Map API

StubHub

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

GET/v1/capture/stubhub
StubHub Seat Map API

SeatGeek

Capture SeatGeek listings, pricing, availability, and seat maps through the shared Tickets.dev marketplace schema.

GET/v1/capture/seatgeek
SeatGeek Seat Map API

TickPick

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

GET/v1/capture/tickpick
TickPick Seat Map 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 Seat Map 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 Seat Map API

Viagogo

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

GET/v1/capture/viagogo
Viagogo Seat Map API

GoTickets

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

GET/v1/capture/gotickets
GoTickets Seat Map API

Paciolan

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

GET/v1/capture/paciolan
Paciolan Seat Map API

ATG Tickets

Capture ATG Tickets box-office inventory: primary seats, published prices and fees, named rows and seats, and the theatre's section and seat maps.

GET/v1/capture/atg
ATG Tickets Seat Map API

ProVenue

Capture ProVenue box-office inventory on tickets.com: primary seats, published prices and fees, named rows and seats, and the venue's section and seat maps.

GET/v1/capture/provenue
ProVenue Seat Map API

GoFevo

Capture Fevo group-sales offers on gofevo.com: primary seats, published prices and fees, named rows and seats, and the offer's section map.

GET/v1/capture/gofevo
GoFevo Seat Map API
Structured JSON

What the seat map API returns

The maps arrive as two hosted URLs on the normal capture response, with venueLayout carrying the sections, rows and seats behind them, next to the venue, the market statistics and every listing they describe.

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

The marketplace's own map, not a generic venue chart

Static venue charts drift from what is on sale. A map captured with the listings reflects the configuration, sections and seats of that event on that night.

Event specific

Stage configurations, curtains, and general admission floors change per event. The map you get is the one drawn for the event you captured.

Joined to live inventory

Section labels in the SVG correspond to the section field on the listings, so you can colour regions by price, depth or availability from the same response.

Seat level where it exists

Where a marketplace draws individual seats, the seat level map and venueLayout carry rows and seat numbers that line up with the seats field on primary listings.

Hosted and ready to render

Both maps are served as SVG from storage.tickets.dev, so they scale on any screen and can be styled with CSS rather than re-drawn.

Use cases

Seat map API use cases

Broker and pricing tools

Show your team where inventory sits and what each section clears at, coloured from the live listings.

Cross-marketplace seat views

Capture the same event on several marketplaces and lay their listings over one map to spot the cheapest route into a section.

Venue capacity and sell-through

Where the marketplace publishes seats, every row and section in venueLayout carries its capacity, so you can set the listings against the house, measure how much of each section is still on sale, and track it across captures as a number or a heatmap on the map.

Consumer apps

Give users the map they already know from the marketplace, with your own pricing, filters and recommendations on top.

Held inventory analysis

Compare the seats a primary map exposes with the seats on sale to see what the box office is holding back.

Seat map data research

Archive the map and venueLayout with each snapshot to study how configurations, section sizes and pricing change over a tour or a season, or compare how the same venue is set up across marketplaces.

FAQ

Seat Map API questions

Is there an API for Ticketmaster seat maps?

Yes. Send a public Ticketmaster event URL with includeVenueMaps=true and the response carries hosted section level and seat level SVG maps for that event alongside every listing.

Which marketplaces return seat level maps?

Any marketplace that draws individual seats on its own event page, including Ticketmaster, SeatGeek, Paciolan, ATG Tickets and ProVenue. Marketplaces that only draw sections return the section level map, and some add a row layer on the seat level URL.

What format are the maps in?

SVG, hosted on storage.tickets.dev. The section level map is the venue overview; the seat level map is the zoomed layer for the same venue. The live examples on this page show the two side by side.

Does the seat map API return the seating chart as data?

Yes. With includeVenueMaps=true the response also carries venueLayout: the venue map as data, every section, row and seat, spelled the way the listings and the maps name them. How deep it goes depends on the marketplace and the venue's map.

Can I get the capacity of a venue or a section?

Yes, where the venue's map goes to the seat. venueLayout then carries a capacity for every row, section and the venue, counted from the seats on the map.

How do I connect the map to the listings?

Section labels in the SVG correspond to the section field on each listing. Group the listings by section, then colour or label the matching regions. Where a marketplace names seats, the seats field on a listing lines up with the seat labels in the seat level map.

Does asking for maps cost extra?

No. A capture is one capture whether or not it renders maps. The maps add a few seconds of render and upload time, which is why they are off by default.

Are the maps cached?

No. The map is rendered from the event page during the capture, so it reflects the configuration on sale at that moment. Each capture produces its own hosted copy.

Can I get a seat map without the listings?

The maps are part of the capture response rather than a separate endpoint. Every capture that asks for maps returns the listings too, so the map always has the inventory to go with it.

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
Ticket Scraping APILive Ticket Inventory APIReal-Time Ticket Price APITicket Events APIAll marketplace APIsPricing