Cirque du Soleil Scraper API
Capture live Cirque du Soleil box-office inventory without building or maintaining your own Cirque scraper. Send a public tickets.cirquedusoleil.com performance link and receive open seats, published prices with the service fee broken out, sections, rows, seat numbers, accessible seating, and section and seat maps as structured JSON.
The API endpoint is https://api.tickets.dev/v1/capture/cirquedusoleil
Cirque du Soleil 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.
{
"status": "Loading example…"}Capture a Cirque du Soleil event
Submit a public event page URL. The request runs the capture and returns one normalized snapshot when it completes.
| Method | Endpoint |
|---|---|
| GET | /v1/capture/cirquedusoleil |
import requests
endpoint = "https://api.tickets.dev/v1/capture/cirquedusoleil"
response = requests.get(
endpoint,
params={"eventUrl": event_url},
headers={"x-api-key": api_key},
)
snapshot = response.json()Query parameters
| Parameter | Type | Description |
|---|---|---|
eventUrl | string required | A public Cirque du Soleil event page URL to capture, from tickets.cirquedusoleil.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. |
includeVenueMaps | boolean 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. |
apiKey | string 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
A Cirque du Soleil shop link is a calendar: picking a date in the shop does not put the performance in the address. Add the date and time you picked with our date and time parameters.
| eventUrl | Captures |
|---|---|
tickets.cirquedusoleil.com/shop/go/<offer>/shop/select | The earliest performance with seats left. |
…/shop/go/<offer>/shop/select?date=YYYY-MM-DD&time=HH:MM | The performance at that date and time, as the shop's calendar shows them (24-hour, venue local time). Without time, the first show that day. |
…/shop/go/<offer>/shop/search?ec=<eventId> | The same performance again: ec takes the eventId an earlier capture returned. The shop does not show this code itself. |
For example: https://tickets.cirquedusoleil.com/shop/go/9c5fd8be-f26f-4942-b331-7a2a20d1fc09/shop/select?date=2026-12-19&time=20:00
Example response
One capture of a real Cirque du Soleil event, trimmed to two listings. Every marketplace returns this same shape, so a parser written once works against all of them.
{
"source": "cirquedusoleil",
"eventId": "DTL261219L",
"eventName": "Cirque du Soleil - Drawn to Life",
"performers": [
{
"performerId": "DTL",
"name": "Cirque du Soleil - Drawn to Life",
"master": true
}
],
"venueId": "DTL",
"venueName": "Walt Disney World Resort",
"venueAddress": "1478 Buena Vista Dr",
"venueCity": "Lake Buena Vista",
"venueState": "FL",
"venueTimezone": "America/New_York",
"eventDateLocal": "2026-12-19T20:00:00-05:00",
"eventDateUtc": "2026-12-20T01:00:00+00:00",
"sourceUrl": "https://tickets.cirquedusoleil.com/shop/go/9c5fd8be-f26f-4942-b331-7a2a20d1fc09/shop/select?date=2026-12-19&time=20:00",
"capturedAt": "2026-10-06T14:24:26.969933+00:00",
"currency": "USD",
"note": "",
"seatLevelUrl": "https://storage.tickets.dev/seatmaps/cirquedusoleil/seat/DTL261219L/1791296666.svg",
"sectionLevelUrl": "https://storage.tickets.dev/seatmaps/cirquedusoleil/section/DTL261219L/1791296666.svg",
"stats": {
"listingCount": 68,
"ticketCount": 375,
"getInPrice": 117.93,
"medianPrice": 166.76,
"avgPrice": 164.25,
"maxPrice": 288.51
},
"listings": [
{
"listingId": "",
"inventoryType": "primary",
"section": "203",
"row": "U",
"quantity": 5,
"ticketPrice": 107.98,
"fee": 9.95,
"totalPrice": 117.93,
"ticketType": "Accessible Adult (13+)",
"sellableQuantities": "1,2,3,4,5",
"group": "Accessible seats",
"seats": "17,18,19,20,21",
"listingNotes": "",
"dealScore": ""
},
{
"listingId": "",
"inventoryType": "primary",
"section": "203",
"row": "U",
"quantity": 3,
"ticketPrice": 107.98,
"fee": 9.95,
"totalPrice": 117.93,
"ticketType": "Accessible Adult (13+)",
"sellableQuantities": "1,2,3",
"group": "Accessible seats",
"seats": "11,12,13",
"listingNotes": "",
"dealScore": ""
}
// …66 more listings
],
"venueLayout": {
"level": "seat",
"capacity": 1575,
"sections": [
{
"section": "101",
"group": "",
"ga": false,
"capacity": 119,
"rows": [
{
"row": "A",
"capacity": 14,
"seats": "1,2,3,4,5,6,7,8,9,10,11,12,13,14"
},
{
"row": "B",
"capacity": 14,
"seats": "1,2,3,4,5,6,7,8,9,10,11,12,13,14"
}
// …6 more rows
]
}
// …11 more sections
]
}
}Real-time Cirque du Soleil 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.
Cirque du Soleil API questions
What does the Cirque du Soleil 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 Cirque du Soleil 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 Cirque du Soleil URLs does it accept?
Any public event page URL from tickets.cirquedusoleil.com. Country domains and subdomains work as well. The match is on the marketplace, not the exact host.
Is the Cirque du Soleil 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 Cirque du Soleil 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 Cirque du Soleil works unchanged against Ticketmaster, StubHub, SeatGeek, TickPick, Vivid Seats, Gametime, Viagogo, GoTickets, Paciolan, ATG Tickets, ProVenue, GoFevo, Spotlight.Vegas and Vegas.com.
How is the Cirque du Soleil 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 Vegas.com 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.