tickets.dev

Vegas.com Scraper API

Capture live Vegas.com show inventory without building or maintaining your own vegas.com scraper. Send the public seat-picker URL for a performance and receive open seats, all-in prices with fees broken out and tax left out, sections, rows, seat numbers, and the theater's section and seat maps as structured JSON.

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

Vegas.com 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%
Loading example…
Primary
Number of tickets
Seating tier
JSON response
{
  "status": "Loading example…"}

Capture a Vegas.com event

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

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

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

Query parameters

ParameterTypeDescription
eventUrlstring
required
A public Vegas.com event page URL to capture, from vegas.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, and fill venueLayout with the sections, rows and seats of the venue. Off by default, because the maps add render and upload time to a request most callers make for pricing alone, so the URLs come back as empty strings and venueLayout at level none 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.

Choosing a performance

Send the seat picker's URL, the one vegas.com shows after you choose a date and time. Its path carries the performance start.

eventUrlCaptures
vegas.com/iv2/las-vegas-shows/<id>/<show>/quantity/<YYYYMMDD-HHMMSS>/…The performance starting at that date and time.

For example: https://www.vegas.com/iv2/las-vegas-shows/6341/magic-mike-live/quantity/20261219-193000/20261219/20261219/false

Example response

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

{
  "source": "vegascom",
  "eventId": "1FMY8-467",
  "eventName": "Magic Mike Live",
  "performers": [
    {
      "performerId": "6341",
      "name": "Magic Mike Live",
      "master": true
    }
  ],
  "venueId": "447",
  "venueName": "Magic Mike Theater",
  "venueAddress": "2535 S. Las Vegas Blvd.",
  "venueCity": "Las Vegas",
  "venueState": "NV",
  "venueTimezone": "America/Los_Angeles",
  "eventDateLocal": "2026-12-19T19:30:00-08:00",
  "eventDateUtc": "2026-12-20T03:30:00+00:00",
  "sourceUrl": "https://www.vegas.com/iv2/las-vegas-shows/6341/magic-mike-live/quantity/20261219-193000/20261219/20261219/false",
  "capturedAt": "2026-10-06T14:13:33.703664+00:00",
  "currency": "USD",
  "note": "",
  "seatLevelUrl": "https://storage.tickets.dev/seatmaps/vegascom/seat/1FMY8-467/1791296013.svg",
  "sectionLevelUrl": "https://storage.tickets.dev/seatmaps/vegascom/section/1FMY8-467/1791296013.svg",
  "stats": {
    "listingCount": 71,
    "ticketCount": 420,
    "getInPrice": 72.8,
    "medianPrice": 120.01,
    "avgPrice": 122.33,
    "maxPrice": 180.45
  },
  "listings": [
    {
      "listingId": "",
      "inventoryType": "primary",
      "section": "200",
      "row": "C",
      "quantity": 5,
      "ticketPrice": 72.8,
      "fee": 0,
      "totalPrice": 72.8,
      "ticketType": "Reserved",
      "sellableQuantities": "1,2,3,4,5",
      "group": "P4-VDC10",
      "seats": "231,232,233,234,235",
      "listingNotes": "",
      "dealScore": ""
    },
    {
      "listingId": "",
      "inventoryType": "primary",
      "section": "220",
      "row": "A",
      "quantity": 3,
      "ticketPrice": 72.8,
      "fee": 0,
      "totalPrice": 72.8,
      "ticketType": "Reserved",
      "sellableQuantities": "1,2,3",
      "group": "P4-VDC10",
      "seats": "271,272,273",
      "listingNotes": "",
      "dealScore": ""
    }
    // …69 more listings
  ],
  "venueLayout": {
    "level": "seat",
    "capacity": 444,
    "sections": [
      {
        "section": "100",
        "group": "",
        "ga": false,
        "capacity": 40,
        "rows": [
          {
            "row": "AA",
            "capacity": 40,
            "seats": "10,9,8,7,6,5,4,3,2,1,40,39,38,37,36,35,34,33,32,31,30,29,28,27,26,25,24,23,22,21,20,19,18,17,16,15,14,13,12,11"
          }
        ]
      }
      // …11 more sections
    ]
  }
}

Real-time Vegas.com 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.

Vegas.com API questions

What does the Vegas.com API return?

One normalized snapshot of the event as it looks right now: every open seat with its section, row, seat number, published price 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 seats.

Why use a Vegas.com scraper 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 Vegas.com URLs does it accept?

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

Is the Vegas.com data live or cached?

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

Does Vegas.com 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 Vegas.com works unchanged against Ticketmaster, StubHub, SeatGeek, TickPick, Vivid Seats, Gametime, Viagogo, GoTickets, Paciolan, ATG Tickets, ProVenue, GoFevo, Spotlight.Vegas and Cirque du Soleil.

How is the Vegas.com 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.

Does the response include the venue's seating chart and capacity?

Yes. Ask for venue maps and venueLayout carries the venue map as data: every section, row and seat, with capacities counted from the seats. Names match the listings and the maps, so a listing binds to its row and seats without a lookup table.

Are there any restrictions on how I can use the data?

No. 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.

Other marketplace APIs

The same endpoint shape and the same response schema cover every marketplace we support: Ticketmaster API, StubHub API, SeatGeek API, TickPick API, Vivid Seats API, Gametime API, Viagogo API, GoTickets API, Paciolan API, ATG Tickets API, ProVenue API, GoFevo API, Spotlight.Vegas API, and Cirque du Soleil API. Start with the ticket scraping API, explore live ticket inventory, real-time ticket pricing and seat maps, see every ticket marketplace API, check per-capture pricing, or talk to us about volume.