Hellotickets Scraper API
Capture live Hellotickets inventory without building or maintaining your own Hellotickets scraper. Send a public event URL from hellotickets.com or any of its country sites, such as hellotickets.es or hellotickets.de, and receive every listing with its section, row, quantity and price, and the venue's section map, as structured JSON in that site's currency, captured live and never cached.
The API endpoint is https://api.tickets.dev/v1/capture/hellotickets
Hellotickets scraper API for live inventory
Each request captures current listing-level inventory with sections, rows, quantities, prices, and optional seat maps in the same normalized JSON used across every marketplace.
{
"status": "Loading example…"}Capture a Hellotickets 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/hellotickets |
import requests
endpoint = "https://api.tickets.dev/v1/capture/hellotickets"
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 Hellotickets event page URL to capture, from hellotickets.com, hellotickets.es, hellotickets.de or hellotickets.fr. Any country domain or subdomain of those works as well. The match is on the marketplace name, not the exact host. A URL from any other host returns 400 marketplace_mismatch without running a capture. |
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. |
Example response
One capture of a real Hellotickets event, trimmed to two listings. Every marketplace returns this same shape, so a parser written once works against all of them.
{
"source": "hellotickets",
"eventId": "2540740",
"eventName": "Arsenal vs. Tottenham Hotspur",
"performers": [
{
"performerId": "1835",
"name": "Arsenal FC",
"master": true
},
{
"performerId": "756",
"name": "Tottenham Hotspur FC",
"master": false
}
],
"venueId": "2101",
"venueName": "Emirates Stadium",
"venueAddress": "75 Drayton Park",
"venueCity": "London",
"venueState": "Greater London",
"venueTimezone": "Europe/London",
"eventDateLocal": "2027-05-01T21:00:00+01:00",
"eventDateUtc": "",
"sourceUrl": "https://www.hellotickets.com/united-kingdom/london/sports/arsenal-fc-tickets/2027-05-01,1500/2540740/2",
"capturedAt": "2026-11-18T23:22:56.524159+00:00",
"currency": "USD",
"note": "Date and time to be announced.",
"seatLevelUrl": "",
"sectionLevelUrl": "https://storage.tickets.dev/seatmaps/hellotickets/section/2540740/1795044175.svg",
"stats": {
"listingCount": 1680,
"ticketCount": 3945,
"getInPrice": 744,
"medianPrice": 3223,
"avgPrice": 3175.11,
"maxPrice": 34749
},
"listings": [
{
"listingId": "v1.EskJxtpWIPsBpJOt6j-Bjz8OX3FZIruVW0X3l2I",
"inventoryType": "resale",
"section": "Shortside Upper Tier",
"row": "",
"quantity": 1,
"ticketPrice": 744,
"fee": 0,
"totalPrice": 744,
"ticketType": "Mobile Ticket",
"sellableQuantities": "1",
"group": "Shortside Upper Tier",
"seats": "",
"listingNotes": "",
"dealScore": ""
},
{
"listingId": "v1.EskJxtpWIPsBoJOt6mXUzDmRMS36QYU__d_ydng",
"inventoryType": "resale",
"section": "Shortside Upper Tier",
"row": "",
"quantity": 2,
"ticketPrice": 745,
"fee": 0,
"totalPrice": 745,
"ticketType": "Mobile Ticket",
"sellableQuantities": "2",
"group": "Shortside Upper Tier",
"seats": "",
"listingNotes": "",
"dealScore": ""
}
// …1,678 more listings
],
"venueLayout": {
"level": "section",
"sections": [
{
"section": "112",
"group": "Longside Upper Tier",
"ga": false,
"rows": []
}
// …271 more sections
]
}
}Every field is described in the API reference and in the OpenAPI 3.1 spec, which Postman, client generators and coding agents can read directly.
Real-time Hellotickets pricing and availability
Store successive captures to monitor new and removed listings, price changes, quantity movement, and inventory depth over time. The ticket price API guide covers price comparison, price alerts, resale analytics, and dynamic pricing workflows.
For working code, see how to track ticket prices across marketplaces for scheduled captures and price history, and how to build price and inventory alerts for notifications when listings change.
Hellotickets API questions
What does the Hellotickets API return?
One normalized snapshot of the event as it looks right now: every listing with its section, row, quantity and price, 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 Hellotickets 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, 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 Hellotickets URLs does it accept?
Any public event page URL from hellotickets.com, hellotickets.es, hellotickets.de and hellotickets.fr. Country domains and subdomains work as well. The match is on the marketplace, not the exact host.
Is the Hellotickets 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 Hellotickets 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 Hellotickets works unchanged against Ticketmaster, StubHub, StubHub International, SeatGeek, TickPick, Vivid Seats, Gametime, Viagogo, GoTickets, TicketNetwork, Paciolan, ProVenue, GoFevo, Telecharge, Broadway Direct, ATG Tickets, Cirque du Soleil, Vegas.com and Spotlight.Vegas.
How is the Hellotickets 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?
To the section. Ask for venue maps and venueLayout carries the venue map as data: every section, named the way the listings and the map name them.
Are there any restrictions on how I can use the data?
No. A capture only reads public data: the listings, prices 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, StubHub International API, SeatGeek API, TickPick API, Vivid Seats API, Gametime API, Viagogo API, GoTickets API, TicketNetwork API, Paciolan API, ProVenue API, GoFevo API, Telecharge API, Broadway Direct API, ATG Tickets API, Cirque du Soleil API, Vegas.com API, and Spotlight.Vegas API. To line up one event across several of them, follow our ticket price comparison guide. 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.