eBay Scraper: Extract Listings, Auctions, and Sold Prices

1.eBay listing fields worth capturing

The right field set depends on the use case. Resellers tracking arbitrage opportunities care about the spread between current bid and Buy It Now price. Brand protection teams need seller identity and unauthorized listing detection. Pricing analysts building valuation models need sold comps with condition and shipping normalized out.

Item specifics — the structured table of attributes like Storage Capacity, Color, or Compatible Model — are often more useful than free-text titles for product matching across listings. Capture them as a key-value map rather than a flat string.

Watchers count is a soft demand signal. eBay shows it on listings above a threshold; when absent, treat it as zero rather than null — the field is conditionally rendered, not always missing.

• Item ID — numeric suffix from /itm/ URL, stable across edits
• Title, subtitle (when present), and item specifics table as key-value pairs
• Listing format: auction, Buy It Now, Best Offer, or combination
• Current price or current bid amount with currency code
• Bid count and auction end time (UTC-normalized)
• Buy It Now price when auction and BIN coexist on the same listing
• Shipping cost, carrier, and estimated delivery window
• Condition label and seller-provided condition description
• Seller username, feedback score (raw count), and positive feedback percentage
• Quantity available and quantity sold for multi-unit fixed-price listings
• Watchers count when rendered
• Sold comps: final sale price, end date, and condition for completed listings

2.eBay URL patterns by region and listing type

Item view URLs — /itm/NUMERIC — are the most stable entry point and have survived multiple eBay front-end redesigns. Search and category browse pages carry heavier bot-detection pressure and are more likely to trigger challenges at volume.

Regional eBay TLDs share the same item ID namespace but maintain separate catalogs, seller accounts, and currency contexts. A proxy region should match the TLD you are targeting: use residential:uk for ebay.co.uk, residential:de for ebay.de. Mismatched proxy regions can trigger geo-redirect responses that return the wrong regional site.

Sold listing search is the primary source for comp data. The LH_Sold=1&LH_Complete=1 parameter combination filters to completed, sold listings only. LH_Complete=1 alone includes unsold completed listings — useful for sell-through rate analysis but noisier for pricing.

• US item view: https://www.ebay.com/itm/176543210987
• UK item view: https://www.ebay.co.uk/itm/176543210987
• DE item view: https://www.ebay.de/itm/176543210987
• US sold comps search: https://www.ebay.com/sch/i.html?_nkw=iphone+13&LH_Sold=1&LH_Complete=1
• US active search with category: https://www.ebay.com/sch/i.html?_nkw=vintage+camera&_sacat=625
• Seller store front: https://www.ebay.com/str/sellerstorename
• Product catalog page (catalog-backed): https://www.ebay.com/p/123456789
• Paginated search: append &_pgn=2, &_pgn=3 — keep inter-page delay ≥ 3 s

3.eBay item page DOM structure and CSS selectors

eBay's item view page uses a component-based layout with predictable class names that have been stable across the Harmony design system. Price is rendered inside div.x-price-primary — the primary span.ux-textspans inside it holds the formatted amount including currency symbol. For auction listings, a secondary span.ux-textspans--BOLD near the bid section holds the bid count.

Item specifics live in div.ux-layout-section--item-specifics. Each row is a dl element; dt holds the attribute name, dd holds the value. Iterating dl elements gives you the full specifics map without relying on positional indexing.

The seller block is in div.ux-seller-section. The anchor tag inside span.ux-seller-section__item--seller holds the username as link text. Feedback score and positive percentage are in adjacent span elements within div.ux-seller-section__item--feedback. Shipping details — cost, carrier, and estimate — are in div.ux-labels-values--shipping, with individual span.ux-textspans elements for each piece of information.

Multi-variation listings (e.g., a shirt in multiple sizes and colors) render a variation selector above the price. The price shown before a variation is selected may be a range. Select a specific variation via URL parameter _var= if you need a single SKU price without JavaScript interaction.

Auction end time appears in span.ux-timer__text for active auctions with time remaining, and as a static timestamp in a nearby span with a data-end-date attribute on listings close to ending. Always prefer the data attribute over parsed text for machine-readable timestamps.

4.eBay bot detection: behavior and mitigation

eBay's bot management applies different pressure depending on the endpoint. Single item view pages (/itm/) at moderate request rates from residential IPs are the lowest-friction surface. Search endpoints (/sch/i.html) — especially sold listing search — are crawled heavily by many actors and receive stricter treatment: CAPTCHA challenges, IP blocks, and redirect loops are common from datacenter ranges.

Active auction pages present an additional challenge: bid count and time-remaining fields update via WebSocket or periodic XHR polling. A static HTML scrape captures the state at request time. If you need near-real-time bid tracking, use mode js_rendering with a js_wait_selector targeting the bid count element to ensure the initial JS render has completed before extraction.

Regional TLDs (ebay.de, ebay.fr, ebay.co.uk) share eBay's bot management infrastructure but maintain separate rate limit buckets. A burst against ebay.com does not consume your quota against ebay.co.uk, but the detection heuristics are identical.

The OmniScrape Web Unlocker handles CAPTCHA solving and challenge bypass automatically when enable_solver: true is set. For sold listing search — the highest-friction endpoint — combine residential proxy matching the TLD region with enable_solver: true and keep inter-request intervals above 3 seconds.

• CAPTCHA and redirect challenges on /sch/i.html sold search at volume
• IP-level blocks on datacenter ranges for search endpoints
• Dynamic bid count and timer updates via JavaScript on active auctions
• Geo-redirect responses when proxy region mismatches TLD
• Layout variants: auction, fixed price, multi-variation, catalog-backed — each with slightly different DOM
• Intermittent 429 responses on rapid sequential item view scrapes

5.Scrape an active eBay listing

Item view pages are the lowest-friction starting point. Use mode auto — OmniScrape will attempt a fast HTTP fetch first and escalate to browser rendering only if the response indicates a challenge or incomplete render. This keeps costs and latency low for the majority of item pages that serve complete HTML without JavaScript gating.

Match the proxy region to the eBay TLD. For ebay.com, use residential:us. The css_selectors map below covers the primary fields for both auction and fixed-price listings. Fields absent from the current listing type — such as bid_count on a fixed-price item — will return empty strings in body.data.css_extracted rather than errors.

The response HTML is in body.data.content. For css_extractor mode, extracted field values are in body.data.css_extracted as a key-value map matching your selector keys.

1234567891011121314151617181920{
  "url": "https://www.ebay.com/itm/176543210987",
  "mode": "auto",
  "output_format": "css_extractor",
  "proxy": "residential:us",
  "enable_solver": true,
  "css_selectors": {
    "title": "h1.x-item-title__mainTitle span.ux-textspans",
    "price": "div.x-price-primary span.ux-textspans",
    "bid_count": "div.x-bid-count span.ux-textspans",
    "auction_end": "span.ux-timer__text",
    "bin_price": "div.x-bin-price span.ux-textspans",
    "shipping": "div.ux-labels-values--shipping span.ux-textspans",
    "condition": "div.x-item-condition-text span.ux-textspans",
    "seller": "div.ux-seller-section__item--seller a",
    "feedback_score": "div.ux-seller-section__item--feedback span.ux-textspans",
    "watchers": "div.ux-watchers span.ux-textspans",
    "quantity_available": "div.x-quantity__availability span.ux-textspans"
  }
}

6.Scrape sold listing search results

Sold comps data lives on eBay's search results pages filtered by LH_Sold=1&LH_Complete=1. Each result card is an li.s-item element inside ul.srp-results. The sold date appears in a span with class POSITIVE inside the tagblock — it renders as relative text ('Sold Jan 15, 2025') that you will need to parse into a structured date.

Sold search is the highest-friction endpoint. Use enable_solver: true and a residential proxy. Keep pagination slow — increment _pgn by one and wait at least 3–5 seconds between pages. Rapid sequential page fetches are the most common trigger for IP-level blocks on this endpoint.

Each result card link points to the completed listing's /itm/ URL. You can follow those links to extract full item specifics and seller details not available in the search card, but that doubles your request volume — only do it when the card data is insufficient.

123456789101112131415{
  "url": "https://www.ebay.com/sch/i.html?_nkw=vintage+camera&LH_Sold=1&LH_Complete=1&_pgn=1",
  "mode": "auto",
  "output_format": "css_extractor",
  "proxy": "residential:us",
  "enable_solver": true,
  "css_selectors": {
    "titles": "li.s-item h3.s-item__title",
    "sold_prices": "li.s-item span.s-item__price",
    "sold_dates": "li.s-item span.s-item__title--tagblock span.POSITIVE",
    "conditions": "li.s-item span.SECONDARY_INFO",
    "shipping": "li.s-item span.s-item__shipping",
    "links": "li.s-item a.s-item__link"
  }
}

7.Auction timing, bid tracking, and currency normalization

Auction end time is the most operationally sensitive field. Parse it from the data-end-date attribute on the timer element when available — it is an ISO 8601 string that does not require text parsing. The span.ux-timer__text display string ('2h 14m remaining') is for human display only; store the absolute UTC timestamp instead.

Active auctions update bid count and current price via JavaScript polling. A static HTML scrape captures the state at the moment of the request. For monitoring auctions in the final minutes — where sniping behavior drives rapid price changes — use mode js_rendering with js_wait_selector set to div.x-bid-count to ensure the JavaScript render has settled before extraction. Keep refresh intervals above 30 seconds to avoid rate limits.

Currency normalization is mandatory in multi-region pipelines. ebay.co.uk returns GBP, ebay.de returns EUR, ebay.com.au returns AUD. The currency symbol is embedded in the price text alongside the amount. Extract the ISO currency code from the regional TLD mapping rather than parsing the symbol — symbols are ambiguous ($, £, € can appear on multiple regional sites depending on proxy behavior). Store raw amount and currency code separately; apply FX conversion at query time, not at ingest time, so historical data remains accurate as rates change.

Best Offer listings do not expose the accepted offer price — only the asking price is public. If a listing ends without a visible sold price on the completed page, it likely sold via Best Offer. Flag these records separately rather than treating the asking price as the sale price.

8.Marketplace monitoring pipeline design

The natural primary key for eBay data is the numeric item ID from the /itm/ URL suffix. Item IDs are immutable — a seller cannot change the ID by editing the listing. Use item ID as the deduplication key across your scrape runs.

Listing lifecycle management is critical. Auctions end; fixed-price listings sell out or expire. A 404 response on an /itm/ URL means the listing is gone. A page that loads but shows an 'ended' banner — detectable via a CSS selector on div.vi-notify-msg or similar — means the listing completed. Mark records inactive on either signal; do not delete them, as historical price data retains value for comp analysis.

Separate your active-listing dataset from your sold-comps dataset at the schema level. Active listings change (price edits, relists, quantity updates). Sold comps are immutable once captured — a completed listing's final price does not change. Mixing them in the same table with the same update logic creates correctness problems.

For large item ID lists, async worker patterns distribute load and respect rate limits. See web scraping with Python for queue-based worker implementations. For the broader price monitoring use case — alert thresholds, time-series storage, competitor tracking — see price monitoring web scraping.

Deduplication on sold comps search requires care: the same completed listing can appear on multiple search result pages if your keyword matches multiple item specifics. Deduplicate on item ID after collection, not during.

9.eBay API, developer policies, and legal considerations

eBay provides official APIs through the eBay Developers Program — the Browse API, Buy API, and Finding API cover a significant portion of item search and detail retrieval use cases with structured responses and no scraping overhead. Evaluate whether the official API meets your data needs before building a scraping pipeline.

eBay's User Agreement restricts automated access and commercial redistribution of listing data. The practical and legal risk profile differs substantially between internal pricing research (using sold comps to value inventory) and building a product that republishes eBay listing data to third parties. Get legal review for any commercial application.

Robots.txt on ebay.com disallows crawling of search and sold listing pages for most user agents. This is a policy signal, not a technical block, but it is relevant to your legal and compliance assessment.

Rate limiting your scraper is both a technical necessity and a courtesy. eBay's infrastructure serves millions of real users; aggressive scraping degrades that experience and accelerates countermeasures that affect all automated access. Design for sustainable throughput — a pipeline that runs reliably at moderate speed is more valuable than one that saturates quickly and gets blocked.