StubHub Scraper — Ticket Prices, Events, Performers & Venues

Extract event and ticket pricing data from StubHub — the world's largest ticket resale marketplace — covering concerts, sports, theater, comedy, and festivals worldwide. Search by keyword, artist, team, venue, or category; resolve any entity to its StubHub id; pull full event rows with dates, venues, floor prices, and availability; and capture ticket listings as individual Dataset rows.

Use this Actor as a practical StubHub API alternative for ticket price monitoring, resale market research, event discovery, performer tour tracking, and venue analysis. A managed anti-bot stack (real-Chrome browser + residential egress + unlocker fallback) handles StubHub's DataDome / AWS WAF protection for you — no proxies or StubHub account required.

• 10 collection modes: search, performer (with city filter), venue, grouping (tours/shows), category, explore-by-geo, event detail + ticket listings, plus entity helpers — suggest (autocomplete), categories (live category tree), and cities (performer city presets)
• Rich event rows: title, date/time, venue (name/city/country), floor price + currency, availability state, sold-out flags, on-sale scheduling, under-$100 flag, favorites count
• Performer & venue intelligence: genres, Spotify top track, hottest event, hourly viewer counts, venue capacity and geo coordinates
• Price & inventory tracking: snapshot complete listing-row sets per run, diff across scheduled runs, webhook alerts on price drops and sold listings
• Pay-per-row pricing: $0.005 per run start + $3.00 per 1,000 results (volume tiers down to $1.60) — prices did not change; each Dataset row is one billed entity

Free Apify-plan users (developer policy): 10 runs / 200 results per run.

Unofficial community Actor — not affiliated with StubHub Inc. Collects only publicly available page data. You are responsible for complying with StubHub terms and applicable law. Checkout / purchase flows are out of scope.

---

What StubHub data can I extract?

Data	Search / Suggest	Performer / Cities	Venue / Grouping / Category	Event detail
Event id / title / URL	✅	✅	✅	✅
Date, time & door time	✅	✅	✅	✅
Venue name / city / country / address	✅	✅	✅	✅
Floor price & currency (lowestPrice)	✅	✅	✅	✅
Availability state & sold-out message	✅	✅	✅	✅
On-sale scheduling (onSaleDateTimeData)	✅	✅	✅	—
Under-$100 & parking flags	✅	✅	✅	—
Performer names / event type	✅	✅	✅	✅
Entity resolution (ids for performers, venues, categories)	✅ (suggest)	—	—	—
Performer profile (genres, Spotify top track, hottest event, viewer counts)	—	✅	—	—
Venue profile (capacity, lat/lon, address, categories)	—	—	✅	—
City presets (lat/lon, event count, cityId)	—	✅ (cities)	—	—
Live category tree (Sports / Concerts / Theatre & Comedy + 36 subs)	—	—	✅ (categories)	—
Ticket listings (seat-level: section/row/seat, price, quantity, deal score)	—	—	—	✅*
Price/inventory change tracking	—	—	—	✅*

*Event listings use available page cards and in-session inventory responses. Availability varies by event and session. With includeListings=true, every ticket listing is emitted as its own row (rowType: "listing"); inventoryComplete=true means that run covered the event's complete observed inventory.

Rows include inventoryStatus: not_requested, unavailable, partial, empty, or complete. unavailable means inventory could not be established, not sold out. empty requires an explicit zero total from the inventory surface. listingTotal is omitted when the source does not report it. A run may deliver useful rows with RUN_SUMMARY.status=SUCCEEDED while partial=true.

---

Popular use cases

1. Ticket price monitoring & drop alerts

In plain English: point the Actor at a hot event URL on a schedule → get notified when prices drop or seats sell out.

You give: mode=event, the canonical eventUrl, trackChanges=true, and your alertWebhookUrl.

You get back (per run):

Field	Example
Event	NBA Preseason: Nuggets at Lakers
Floor price	$77.17 USD
Listings snapshot	3 Dataset rows (rowType=listing, $109–$250)
Changes	priceDrops: 1, newListings: 2

2. Performer tour tracking

In plain English: follow an artist's whole tour — every city, date, venue, and floor price — in one table.

You give: mode=performer, the performer id (find it with mode=suggest), optional citySlug+cityId to filter one city, maxPages for full tours.

You get back: one row per show (Stockholm, London, Mexico City, Tokyo…). Set includePerformerProfile=true to also bill and return a performer profile row with genres, Spotify top track, hottest event, and hourly viewer demand.

3. Venue research & capacity intelligence

In plain English: build a venue database — capacity, address, geo coordinates, and everything playing there.

You give: mode=venue, a venue id (e.g. 601 for Crypto.com Arena).

You get back: the upcoming-events table. Set includeVenueProfile=true to also bill and return a venue profile row (capacity, lat/lon, full address, categories).

4. Event discovery & market research

In plain English: search any keyword ("nba", "taylor swift", "hamilton") and export a clean dataset for your pricing models, event calendars, or dashboards.

You give: mode=search, query, maxResults (up to 500/run on paid plans).

You get back: deduped event rows with dates, venues, countries, floor prices, availability, and inventory signals — ready for Excel, CSV, or JSON export.

---

More Actors like this

Scraping another ticket or event site? Use the dedicated Actor — structured fields, better coverage, usually lower cost.

Tickets & Events

• SeatGeek Scraper — Events, performers, venues & listings
• Ticketmaster Scraper — Events, artists, venues & categories
• Eventim Scraper — CTS Eventim events & tickets, 40+ countries
• Eventbrite Scraper — Events, tickets, venues & organizers
• Polymarket Scraper — Prediction market events, odds & volume

Beyond tickets — top picks by category

• Jobs: LinkedIn Jobs Scraper · Indeed Jobs Scraper
• E-commerce: Amazon Search Scraper · Walmart Product Scraper
• Real estate: Zillow & Zumper Scraper · Rightmove Scraper
• Travel: Booking.com & Airbnb Scraper · Expedia Scraper
• Leads & local: Google Maps Scraper
• Ads intelligence: Facebook Ad Library Scraper · TikTok Ads Scraper
• Social: TikTok Scraper · Reddit Scraper
• Any other protected site: Stealth Web Scraper

→ Full catalog in Related Actors below, or browse apify.com/lentic_clockss.

---

How to use (no code required)

1. Click "Try for Free" at the top of this page
2. Pick a mode (e.g. search) and enter a query or an id
3. Don't know an id? Run mode=suggest with a name first — it returns the numeric ids StubHub uses
4. (Optional) Set proxyCountry (e.g. gb) when targeting country-specific inventory
5. Click Start — results appear in the Dataset tab within minutes

Download as CSV, Excel, or JSON. That's it.

Input examples

Search events:

{
  "mode": "search",
  "query": "taylor swift",
  "maxResults": 20
}

Performer with city filter:

{
  "mode": "performer",
  "performerId": "714235",
  "performerSlug": "the-weeknd",
  "citySlug": "london",
  "cityId": "4031",
  "maxResults": 20
}

Event detail with listings + price tracking:

{
  "mode": "event",
  "eventUrl": "https://www.stubhub.com/los-angeles-lakers-los-angeles-tickets-10-16-2026/event/161677522/",
  "includeListings": true,
  "trackChanges": true,
  "alertWebhookUrl": "https://your-webhook.example/alerts"
}

---

Modes

Mode	What it scrapes	Required input
search	Free-text event search (/secure/search)	query
performer	All events for an artist/team; optional city filter; opt in to a billed performer profile row with includePerformerProfile=true	performerId (e.g. 714235) or performerSlug; optional citySlug+cityId
venue	Upcoming events at a venue; opt in to a billed venue profile row with includeVenueProfile=true	venueId (e.g. 137012189)
grouping	Events in a tour/show grouping	groupingId (e.g. 130466796)
category	Events in a category	categoryId (slug-only falls back to search)
explore	Paginated events near a location	city (preset) or lat+lon
event	Single event detail; with includeListings=true, one Dataset row per ticket listing	eventId or eventUrl (canonical URL from your browser works best)
suggest	Entity autocomplete — resolves a query to performers/venues/categories with ids and URLs (great for finding ids)	query
categories	Live category tree — 3 top categories (Sports / Concerts / Theatre & Comedy) and 36 subcategories with ids and URLs	—
cities	City preset harvest — every city a performer plays in, with lat/lon, event count, and the citySlug/cityId pair needed for performer city filters	performerId or performerSlug
sitemap	Catalog discovery — the public new-sitemap tree (~2.22M event / performer / venue / category URLs) read with no credential session. Returns seed rows (eventId, canonical url, slug, eventDate) you can feed back into event/detailUrls. Use sitemapKinds to filter (event/performer/venue/category) and sitemapChildLimit to bound the fetch (1–51 child sitemaps, 45k URLs each). Set sitemapPool=true to harvest the full tree (all 51 children) streamed to a JSONL seed-pool file under the worker state dir — the run then returns a small preview + seedPool {path, rows, urlsScanned} in warnings instead of buffering ~2.2M rows into the dataset.	—
(override)	Any explicit StubHub URLs	startUrls / detailUrls / listingIds

Explore mode: uses the public event-list response with the requested coordinates and actual page metadata. Fields vary by surface; list aggregates are not individual ticket listings. listCoverage reports emitted rows versus the reported total.

UK and Europe (host=stubhub.co.uk and .ie / .de / .fr / .es / .nl / .com.au): these hosts are a separate inventory site from stubhub.com. Pass the event URL on that host. Do not rewrite a UK or European event id onto stubhub.com — the same number is a different event there, or a 404. .com.au follows through to the Ireland storefront. stubhub.com, stubhub.ca, and viagogo.com stay on the existing collection route.

Finding ids: use mode=suggest with a name to resolve performers/venues/categories to their numeric ids, or copy them from any StubHub URL — /{slug}-tickets/performer/{performerId}, /{slug}-tickets/venue/{venueId}/, /{slug}-tickets/grouping/{groupingId}, .../event/{eventId}/. For a performer's city filter ids, run mode=cities.

Deep pagination and row budgets: explore uses its page parameter. Other list surfaces use available page data and browser pagination when needed. maxResults is the most Dataset rows for each query, URL, or ID (default 70); larger values are collected in parts of up to 70. Event, entity, optional profile, and ticket-listing rows all share the budget for their input. The whole run stops at your maximum total charge, and free Apify plans are capped at 200 rows per run and 10 runs. venueComplete enables bounded performer-page expansion; venueUnionMaxPerformers and venueUnionMaxDetailChecks control its cost.

Venue identities: input venueId is the ID in the venue page URL. Outputs preserve that as venuePageId and retain the distinct hydration venueId. Address, region, postal code, coordinates and capacity are returned when present. Venue phone/email absence is explicit; platform contact addresses are not venue contacts.

Seat ranges and maps: event mode with includeListings=true extracts card section, row, seller seat range (seatRange), price, delivery and view information when present. Each ticket listing becomes one row. id is the authoritative listingId when exposed; label-only cards use an event-scoped deterministic key and keep listingKey/identitySource so the limitation stays explicit. With includeSeatMap=true, map diagnostics remain separate from ticket availability.

Collection route: acquisitionMode=auto selects available public list routes with browser fallback. browser retains the browser-only route. Run diagnostics include route outcomes, list coverage, map status and browser profile. Field availability remains source-dependent.

---

What you get back

Row layout change

includeListings=true now writes one Dataset row per ticket listing. The old layout placed a listings.listings[] array inside one event row; the current Actor no longer does that. Each listing row includes:

• rowType: "listing"
• id (the listing id, or an event-scoped deterministic key when StubHub exposes only a label)
• listingId / listingKey, section, row, seat, quantity, price and currency
• copied parent fields such as eventId, eventTitle, event date/time, venue, address/geo and canonical URL
• listingTotal, listingOffset, inventorySourceComplete and inventoryComplete

When includeListings=false, event and helper modes still emit one row per event/entity and carry rowType (event, performer, venue, suggestion, category, or city).

Every event or listing row carries stable, analysis-ready parent fields:

• Identity — eventId, title, canonical url, eventType (MusicEvent / SportsEvent / TheaterEvent)
• Schedule — datetimeLocal, doorTime, formattedDate/formattedTime, date/time confirmation flags
• Venue — venueName, venueCity, venueCountry(Code), street/门牌 on address after enrichDetails (JSON-LD streetAddress)
• Leads — phones, emails, address, org, leadAbsences (see below). StubHub venue pages have no box-office phone/email.
• Inventory signals — eventAvailabilityState, hasActiveListings, soldOutMessage, isUnderHundred, isParkingEvent, aggregateFavorites, onSaleDateTimeData
• Context — performerNames, mode context (performerId, cityId, …), scrapedAt, sourceLayer (which extraction layer produced the row)

Non-event rows are typed via rowType: listing, suggestion, category, city, plus performer / venue profile rows.

Output example (listing row)

{
  "rowType": "listing",
  "id": "3328712939",
  "listingId": "3328712939",
  "eventId": "159358887",
  "eventTitle": "The Weeknd",
  "title": "The Weeknd",
  "eventType": "MusicEvent",
  "datetimeLocal": "2026-08-09T19:30:00",
  "venueName": "Strawberry Arena (formerly Friends Arena)",
  "venueCity": "Stockholm - Solna",
  "venueCountryCode": "SE",
  "section": "Floor A",
  "row": "7",
  "quantity": 2,
  "price": 109.0,
  "priceCurrency": "USD",
  "listingOffset": 0,
  "listingTotal": 53,
  "inventoryComplete": false,
  "url": "https://www.stubhub.com/the-weeknd-stockholm-tickets-8-9-2026/event/159358887/",
  "source": "stubhub",
  "listingSource": "api-post",
  "scrapedAt": "2026-08-09T12:00:00.000000+00:00"
}

Lead / contact fields

Every dataset row includes these keys (empty arrays plus leadAbsences when the site has no value). Samples from 2026-08-19 recon — not redacted.

Field	Type	What it means on StubHub
phones	[{value, type}]	Venue/box-office numbers. Event and venue JSON-LD have no telephone. Help-center +1 (888)-720-9452 is StubHub CS and is not copied onto rows ([] + leadAbsences.phones=本站无).
emails	[{value, type}]	Venue mailbox. Never press.user@viagogo.com or *@stubhub.com. Measured venue/EDP: none.
address	{street, unit, locality, region, postalCode, country, full}	JSON-LD PostalAddress.streetAddress on event LDP and venue. Search index-data is city-only until enrichDetails. Sample: 1111 South Figueroa Street, postal 90015, Crypto.com Arena. unit stays null — the building number is inside street.
geo	{lat, lng}	Venue profile venueLatitude/venueLongitude when index-data survives. Event JSON-LD Place has no geo.
person	{name, role}	Listings are anonymous sellers. No named box-office agent.
org	{name, id?}	Venue name. Use the URL path venue id (/venue/601/), not list eventGrids[].venueId (1934 404s).
web	{website, socials[]}	Venue URL when present. Organization.sameAs is StubHub socials — not stamped onto the venue.
leadSource / leadReveal	enum	search / detail / entity; street is already visible (no show-phone XHR).
leadAbsences	object	Per-subfield 本站无 / 未验证.

Reveal cost

• No click-to-reveal. enrichDetails (default true) fetches each event LDP so search rows get streetAddress.
• Turning it off leaves search cards without street (leadAbsences.address.street=未验证).
• includeListings is a separate, expensive ticket-inventory path. Leave it false unless you need one row per ticket listing.

Honest limitations

Lead	Status	Why
Venue street on LDP/venue	Available	JSON-LD streetAddress
Venue street on search cards	After enrich	index-data has city only
Venue phone/email	本站无	Not on Place JSON-LD or venue body
Platform CS / press mailbox	Filtered	888-720-9452, viagogo/stubhub mail
Named person / venue social	本站无	Anonymous sellers; sameAs is StubHub
stubhub.co.uk deep pages	Degraded	Pure SPA; use .com + proxyCountry=gb

---

Pricing

Pay per Dataset row: $0.005 per run start + $3.00 per 1,000 results. Prices are unchanged. Each event/entity row or ticket-listing row is one billed result; blocked pages and empty runs cost nothing beyond the start fee.

What triggers a charge	Price
Actor start	$0.005 per run
Result (dataset row)	$3.00 per 1,000 results

Store subscription tiers (automatic discount by your Apify plan):

Tier	$/1,000 results	per result
FREE*	$3.00	$0.003
BRONZE	$3.00	$0.003
SILVER	$2.60	$0.0026
GOLD	$2.20	$0.0022
PLATINUM	$2.00	$0.002
DIAMOND	$1.60	$0.0016

*FREE = the pay-as-you-go rate without a Store subscription.

Volume	Estimated cost (FREE/BRONZE)
100 results	~$0.31
1,000 results	~$3.01
10,000 results	~$30.01

The free $5 monthly Apify credit covers roughly 1,600 results — enough to test real workflows before spending anything.

How this compares: building your own StubHub pipeline means fighting DataDome + AWS WAF, managing residential proxies, and maintaining parsers (20+ hours upfront, ongoing maintenance). This Actor: pay only when you scrape, no subscription required.

---

Price & inventory tracking

With trackChanges: true on mode=event, a run whose listing rows cover the complete observed inventory snapshots those rows into a persistent store and diffs them against the previous run:

Only complete inventory observations update tracking snapshots. Partial or unavailable inventory is skipped, so missing pages are not reported as sold tickets.

• newListings / soldListings — inventory velocity (removed listings ≈ sold)
• priceDrops / priceIncreases with per-listing priceChanges
• Optional alertWebhookUrl — get a JSON POST when prices drop or inventory moves (never on the first snapshot)

Schedule the Actor (e.g. hourly) to build a price history for hot events.

---

Connect to your tools

Platform	How to connect
Make.com	Search "Apify" → "Run Actor" → Actor ID: lentic_clockss/stubhub-scraper
n8n	Add Apify node → "Run Actor" action → same Actor ID
Zapier	Apify integration → "Run Actor" trigger
LangChain	ApifyActorsTool("lentic_clockss/stubhub-scraper")
Apify MCP	Ask your AI agent to run the StubHub Scraper actor
Python / Node.js	Apify SDK or direct HTTPS call

API call example

curl "https://api.apify.com/v2/acts/lentic_clockss~stubhub-scraper/runs" \
  -X POST \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode": "search", "query": "bruno mars", "maxResults": 20}'

Results come back via the Apify Dataset API:

GET https://api.apify.com/v2/datasets/{datasetId}/items?format=json

---

FAQ

Is there an official StubHub API? StubHub retired its public developer API years ago; remaining access is partner-only. This Actor is a practical StubHub API alternative that reads the same public pages you see in a browser and returns clean structured rows.

Is StubHub one site or many country sites? www.stubhub.com serves the US/Canada inventory. The UK and European storefronts (stubhub.co.uk, .ie, .de, .fr, .es, .nl, and .com.au via Ireland) are a separate site with their own event ids. Keep those event URLs on their own host.

Do I need my own proxies? No. The managed worker ships its own residential egress and unlocker credentials. proxyCountry optionally pins the egress country (ISO-2) for geo-sensitive inventory.

Are seat-level ticket listings guaranteed? No. Available page cards and in-session inventory responses can provide listing IDs, sections, rows, seats, prices and quantities. Fields depend on the source. Check inventoryStatus and listings.complete rather than assuming an empty or missing block means sold out. Metadata is returned when the event page can be read and validated.

Why do prices appear in different currencies? StubHub localizes prices to the viewer's market. The worker browses from US residential egress by default, so USD is typical; priceCurrency always tells you which currency a row is in.

Can I track a performer's whole tour? Yes — mode=performer with maxPages covers full tours (deep pagination uses a click-through browser session). Add citySlug/cityId from mode=cities to filter one city.

What are the free-plan limits? Free Apify plans: 10 runs total, 200 results per run (developer policy). Paid plans: unlimited runs, up to 500 results per run.

---

Input reference

Parameter	Type	Description
mode	string	search (default), performer, event, venue, grouping, category, explore, suggest, categories, cities
query	string	Free-text query for search / suggest
performerId / performerSlug	string	Performer target for performer / cities
citySlug / cityId	string	City filter for performer (get values from cities mode)
venueId / venueSlug	string	Venue target for venue
groupingId / groupingSlug	string	Tour/show target for grouping
categoryId / categorySlug	string	Category target for category (ids from categories mode)
eventId / eventUrl	string	Event target for event (canonical URL preferred)
host	string	stubhub.com (default) or a bfx host: stubhub.co.uk, .ie, .de, .fr, .es, .nl, .com.au
proxyCountry	string	ISO-2 egress pin, e.g. gb for UK inventory
city / lat / lon	string/number	Geo anchor for explore
maxResults	integer	Rows per query, URL, or ID, 1–500 (default 70; collected in parts of up to 70; free run cap 200)
maxPages	integer	List pages; 2+ uses a click-through browser session
includeListings	boolean	event: extract ticket listings (default false; omitted param is metadata-only)
maxShowMore	integer	event: show-more clicks for listings expansion (0–20)
includePerformerProfile / includeVenueProfile	boolean	Prepend a separately billed entity profile row (default false)
sitemapChildLimit	integer	sitemap: cap child sitemaps fetched, 1–51 (each ~45k URLs; omit for the full tree)
sitemapKinds	array	sitemap: filter emitted rows to event / performer / venue / category / performer_city / url
sitemapPool	boolean	sitemap: harvest the full tree streamed to a JSONL seed-pool file under the worker state dir; the run returns a preview + seedPool meta in warnings (default false)
prewarmSeed	integer	After the credential session issues, fetch this many seed-pool event LDPs as a warmup + bundle-liveness check before the real query (default 0 = off)
enrichDetails	boolean	Fetch event JSON-LD street onto list rows (default true)
trackChanges	boolean	event: snapshot listings and diff across runs
alertWebhookUrl	string	POST target for price/inventory alerts
startUrls / detailUrls / listingIds	array	Explicit URL/id overrides (mode inferred per URL)

---

Free-tier limits (free Apify plan)

Cap	Value
Runs of this Actor	10 total
Results per run	200
Paid Apify plans	Unlimited runs (schema max 500/run)

These limits are set by the Actor developer, not Apify. When the run quota is exhausted the run finishes as SUCCEEDED with a FREE_TIER_LIMIT summary explaining how to upgrade.

Run report error_class values

Failures are reported to the run helper with a canonical fleet error code (contracts/error-codes.json, fleet/1.0) — never a raw exception name. This Actor emits only:

error_class	Meaning here
invalid_request	Input validation failure; free-tier quota rejection
quality_gate_failed	Run finished with zero rows (NoRowsCollectedError)
deadline_exceeded	Platform/job wait timeout
unauthorized	Worker HTTP 401
challenge_detected	Worker HTTP 403 / blocked, captcha, DataDome, AWS-WAF signals
upstream_4xx / upstream_5xx	Other worker HTTP error statuses
stale_attempt	Worker job lost mid-poll (job_not_found)
queue_full	Worker queue stayed full after retries
network_failure	Worker unreachable / connection errors
internal_error	Anything unmapped (also replaces the old abort fallback)

Per-run diagnostics (RUN_SUMMARY → diagnostics)

Worker responses surface pipeline-health fields useful for telling "blocked" apart from "empty market":

Field	Meaning
sessionHealth.state	Burn-pool session state — ok / soft_challenged / cooling / hard_blocked / dead (recon: GeoNode exit-IP burn is the bottleneck, not the credential)
shadowBlocked	true when a 200 returned zero rows where data was expected — a soft block, not an empty result
contractDropped	Rows dropped fail-closed for missing required fields
challengeVendor	Anti-bot fingerprint on a blocked run — aws_waf / datadome / aws_waf+datadome
shapeCanary	Edge-shape probe result — the BFF floor must stay 400; a 200/403 means the gate shape changed
recoveryAllowedPct	Graded-recovery concurrency (1→5→25→100%) after a burn
listingsExtracted / listingsReportedTotal / listingsTruncated	Inventory coverage on event+includeListings
inventory	Counts of emitted event rows by inventory status
discovery	Sitemap-only coverage: actual attempted/successful/failed children, URLs scanned, truncation, completion, and optional seed-pool details. Discovery does not establish prices or stock.

---

Related Actors

All public Actors from lentic_clockss, by category. Click a name to open its Store page.

Tickets & Events

• StubHub Scraper
• SeatGeek Scraper
• Ticketmaster Scraper
• Eventim Scraper
• Eventbrite Scraper
• Polymarket Scraper

Jobs & Freelance

• LinkedIn Jobs Scraper
• Indeed Jobs Scraper
• Upwork Jobs Scraper
• Glassdoor Scraper
• SEEK Jobs Scraper
• Bayt Jobs Scraper
• Freelancer.com Scraper
• Fiverr Gig Scraper
• RemoteOK Jobs Scraper
• Jobicy Remote Jobs Scraper
• Himalayas Jobs Scraper

Real Estate

• Zillow & Zumper Scraper
• Zillow Group Scraper
• Realtor.com Scraper
• Realtor.com Agents Scraper
• Realtor.ca Scraper
• Apartments.com Rental Scraper
• Craigslist Housing Scraper
• realestate.com.au Scraper
• Rightmove Scraper
• SeLoger Scraper
• ImmoScout24 Scraper
• Idealista Scraper
• Immobiliare.it Scraper
• Funda Scraper
• Daft.ie Scraper
• FINN.no Scraper
• Booli Scraper
• Otodom Scraper
• SUUMO Scraper
• Naver Land Scraper
• Hepsiemlak Scraper
• OpenSooq Scraper
• Property Finder Scraper
• Bayut Scraper
• PropertyGuru Scraper
• 99.co Scraper
• Dot Property Scraper

E-commerce & Retail

• Amazon Search Scraper
• Walmart Product Scraper
• eBay Product Scraper
• Shopee Scraper
• Lazada Product Scraper
• MercadoLibre Scraper
• Allegro Scraper
• Cdiscount Product Scraper
• ASOS Product Scraper
• Costco Product Scraper
• Coupang Product Scraper
• Etsy Scraper
• Mercari Japan Scraper
• Rakuten Japan Scraper
• SHEIN Product Scraper
• Target Product Scraper
• Temu Product Scraper
• TikTok Shop Product Scraper
• 1688 Global Product Scraper

B2B & Wholesale Marketplaces

• Europages Scraper
• Kompass Scraper
• IndiaMART Scraper
• GlobalSources Scraper
• DHgate Wholesale Scraper
• Faire Scraper
• Thomasnet Scraper
• MonotaRO Scraper
• iPROS Scraper
• Xometry Scraper

Food Delivery & Grocery

• DoorDash Scraper
• Uber Eats Scraper
• Deliveroo Scraper
• Wolt Scraper
• foodora Scraper
• foodpanda Scraper
• Grab Scraper
• iFood Scraper
• PedidosYa Scraper
• Talabat Scraper
• Rappi Scraper
• Instacart Scraper

Travel & Stays

• Booking.com & Airbnb Scraper
• Booking.com Hotels Scraper
• Airbnb Listings Scraper
• Expedia Scraper
• Trip.com Scraper
• TripAdvisor Scraper
• Agoda Scraper
• Traveloka Scraper
• Travelstart Flights Scraper
• Despegar Scraper

Social & Content

• TikTok Scraper
• Reddit Scraper
• YouTube Research Scraper
• YouTube Shorts Scraper
• Hacker News Scraper

Ads Intelligence

• Facebook Ad Library Scraper
• TikTok Ads Scraper
• Google Ads Transparency Scraper

Local & Maps

• Google Maps Scraper

General Tools

• Stealth Web Scraper
• Email Validator
• Phone Number Validator

→ Browse the full profile: apify.com/lentic_clockss

---

Changelog

0.1 (2026-08-09, later same day)

• Listings rebuilt on the reverse-engineered inventory contract: SSR page-1 cards + IndexShGridOnly JSON pagination inside a managed session — seat-level rows (listingId, section/row/seat, all-in price, quantities, deal score, notes, face value) with complete/fetched/total coverage flags; maxShowMore now maps to pagination steps (10 listings each)
• Geo-pinned listings sessions for currency consistency

0.1 (2026-08-09)

• Initial release: search / performer (+city filter) / venue / grouping / category / explore / event modes
• Entity modes: suggest (autocomplete), categories (live tree), cities (city presets)
• Performer & venue profile rows; rich inventory signals on event rows
• Deep pagination via click-through browser session; proxyCountry geo pin; host multi-TLD plumbing
• Pay-per-event pricing: $0.005 start + $3.00/1,000 results with Store tier discounts