StubHub is the ticketing site that gives a plain HTTP client nothing at all. On 28 September 2026 we fetched stubhub.com through residential exits in the United States and the United Kingdom. The home page answered a client with no JavaScript with 200 OK, 226,417 bytes and zero words of content, from both countries. Rendering the same URL cost 3,238,143 bytes and 35 seconds from the US exit, and produced 4,721 words of event cards; from the UK exit the render produced 398 words. Ticketmaster, measured the same day, hands a plain HTTP client 494 words and twenty structured events. That comparison is the whole decision.
Zero words without a browser, from two countries
The head of the StubHub home page is honest: a title, a description, a self-referencing canonical, and JSON-LD for Organization and WebSite. The body is an application shell. Our SEO audit counted 0 words of extractable text without JavaScript from a US exit and 0 from a UK one, with hasContent: false on both. The response has no h1. It is 226,417 bytes of markup that says nothing until scripts run.
| Fetch | Exit | Status | Bytes | Words | Time |
|---|---|---|---|---|---|
| Home, no JavaScript | United States | 200 | 226,417 | 0 | 22 s under load |
| Home, no JavaScript | United Kingdom | 200 | 226,399 | 0 | 0.8 s |
| Home, rendered | United States | 200 | 3,238,143 | 4,721 | 34.6 s |
| Home, rendered | United Kingdom | 200 | 3,311,395 | 398 | 4.6 s |
Two counters need reconciling. Our audit tool, which drops navigation and card chrome, reported 157 words of body copy on the rendered US page earlier this month. The full rendered markdown, event cards included, is 4,721 words across 182 headings. Both are true: StubHub's rendered home page is a wall of cards with almost no prose. If you want the cards, you want the 4,721; if you want to know whether the page says anything, the answer is 157.
The render is 14 times the bytes and it is all cards
A rendered StubHub home page weighs 3,238,143 bytes, 14.3 times the no-JavaScript response. What arrives for that is 182 event cards: an artist or team, a date, a venue, and a "from" price. It is a discovery surface, and the listing-level data that a price tracker wants (section, row, quantity, all-in price per listing) lives one click deeper, on per-event pages that are also rendered client-side.
That has a direct consequence for the cost table below: at 3.24 MB per render, paying per gigabyte is the expensive way to read StubHub. The web scraping API bills a rendered page at $0.001, which is 2.6 times cheaper than the bandwidth alone at $0.80/GB, and it returns parsed markdown or JSON instead of three megabytes of DOM. On this target the per-page product beats the per-byte product on price, not only on convenience.
The UK exit gets a different StubHub
The same URL rendered through a United Kingdom residential exit came back with 12 sections and 398 words: a localised landing page rather than the 182-card US wall. The no-JavaScript response was byte-for-byte the same shell from both countries; the difference only appears once scripts run and StubHub decides, from the exit IP, which market you are in. robots.txt confirms the structure: it is 14,172 bytes long because it repeats the same eight disallow rules for 61 locale prefixes, from /uk/ and /jp/ to /py/ and /kz/.
So the geo rule on StubHub is strict. Pin the exit to the market whose prices you are recording, or you will be diffing a US card wall against a UK landing page and calling it a trend. This is the opposite of Ticketmaster, where a UK exit gets the identical US page; on StubHub the IP picks the product.
Ticketmaster is the richer public source for the same events
We measured Ticketmaster the same day, with the same exits, and the numbers point one way:
| Measure, 28 September 2026 | StubHub | Ticketmaster |
|---|---|---|
| Home page words, no JavaScript | 0 | 494 |
| Home page bytes, no JavaScript | 226,417 | 559,212 |
| Category page words, no JavaScript | 0 (same shell) | 1,893 on /discover/concerts |
| Structured event data without a browser | none | 20 MusicEvent objects with venue, date, availability |
| Rendered home page bytes | 3,238,143 | 803,145 |
| Official price route | none published | Discovery API, priceRanges, 5,000 calls per day |
For primary inventory, availability and on-sale dates, Ticketmaster is the richer public source by every row, and it costs a quarter of the bytes. The full measurement is in Ticketmaster proxies: 494 words, no browser. StubHub enters the picture for one question only: what the resale market is asking for an event right now. That question needs the render, and it is worth asking only for the events you actually track.
What StubHub's user agreement says
StubHub's Global User Agreement, itself served only to a browser, lists what a user agrees not to do. Two items apply directly: to "use any robot, spider, scraper or other automated means to access our Site or Services for any purpose without our express written permission", and to "bypass our robot exclusion headers, robots.txt rules or any other measures we may use to prevent or restrict access". The agreement forbids automated access without written permission, and nothing in this post changes that; we describe what the site serves so you can decide what to pay for, and we do not help with bulk buying, multiple accounts or evading the marketplace's screening.
Two facts from StubHub's own newsroom explain what a resale price actually is. Sellers set the price; StubHub suggests one from comparable listings, but the number is the seller's. And the sellers are mostly not professionals: StubHub reports that 99% of its sellers are fans and 94% of those sold 10 or fewer tickets in the past year. A resale "from" price is the cheapest of a crowd of individual decisions, which is why it moves hour to hour and why a single snapshot is a reading, not a market.
The search results for this keyword deserve one sentence. Half of the first page, including the Reddit and Hacker News threads, is about StubHub's proxy e-mail aliases, the forwarding addresses it puts between buyers and sellers. That is a different word wearing the same spelling, and it is not what a proxy pool is for.
Cost math with real numbers
Prices from our pricing page: residential proxies from $0.80/GB on the Basic line, and the web scraping API from $0.0002 per page, $0.001 with rendering, billed only on success. A gigabyte is counted as 10^9 bytes.
| Job | Bytes per request | Requests per GB | Cost per request | What you get |
|---|---|---|---|---|
| Home, no JavaScript, residential | 226,417 | 4,417 | $0.00018 | 0 words: do not buy this |
| Home, rendered, US exit, residential | 3,238,143 | 309 | $0.00259 | 182 cards, 4,721 words |
| Home, rendered, UK exit, residential | 3,311,395 | 302 | $0.00265 | 12 sections, 398 words |
| Home, web scraping API, rendered | n/a | n/a | $0.001 | The same DOM, parsed, billed only on success |
| Ticketmaster category page, no JavaScript, residential | 681,189 | 1,468 | $0.00054 | 20 structured events |
The first row is the trap: 4,417 fetches per gigabyte sounds cheap until you notice each one returns nothing. The second is the honest price of a StubHub read, and the fourth is why the API is the right product here rather than raw bandwidth. If you are deciding between the two products in general, web scraping vs API covers the trade-off; on StubHub the arithmetic decides it.
The setting that works on StubHub
- Network: residential, Basic line at $0.80/GB, and only for the render. Nothing in eight fetches challenged the network; the barrier is JavaScript, not IP reputation.
- Fetch mode: rendered. Plain HTTP returns 0 words from either country; the render returns 4,721 words of event cards from the US. Send it through the web scraping API at $0.001 per rendered page, which costs less than the 3,238,143 bytes at per-GB rates.
- Country to pin:
country=usfor US resale prices. A UK exit renders a different page, 398 words instead of 4,721; the IP picks the market on this site. - When the proxy is not enough: for primary inventory and availability, stop reading StubHub and read Ticketmaster, which serves 494 words and 20 MusicEvent objects with no browser. There is no StubHub collector in our catalogue and, given the user agreement, we are not building one.
- Free tier: every account gets $2 of free API usage per month, which is 2,000 rendered StubHub pages through the API.