eBay Sold Items Scraper [Only $2.5/1K💰] | Price Tracker avatar

eBay Sold Items Scraper [Only $2.5/1K💰] | Price Tracker

Pricing

from $2.30 / 1,000 results

Go to Apify Store
eBay Sold Items Scraper [Only $2.5/1K💰] | Price Tracker

eBay Sold Items Scraper [Only $2.5/1K💰] | Price Tracker

Extract eBay sold items data — final sold prices, shipping and total costs per completed listing — for price tracking and resale research. Search by keyword on ebay.com, or paste URLs from any eBay marketplace. Deep scan adds category path and item specifics. Only $0.0025 per result.

Pricing

from $2.30 / 1,000 results

Rating

0.0

(0)

Developer

Ahmed Jasarevic

Ahmed Jasarevic

Maintained by Community

Actor stats

0

Bookmarked

38

Total users

4

Monthly active users

12 days ago

Last modified

Security

Limited permissions

Share

eBay Sold Items Scraper - Completed Listings, Prices and Market Comps

The eBay Sold Items Scraper collects completed-listing and sold-price evidence from eBay for resale comps, price tracking and inventory research. Supply a keyword or a set of eBay search URLs and receive structured rows with item IDs, titles, sold prices, currency, sale dates and listing URLs.

eBay increasingly walls automated search traffic, so the current build can also fall back to public buyer feedback comps and write a diagnostic probe row when the search surface is blocked. This makes the dataset useful for market evidence while keeping failures visible instead of silently returning an empty run.

Main Use Cases for eBay Resale Comps

  • Resale comps - benchmark what similar items actually sell for before buying or pricing inventory.
  • Price tracking - monitor completed-listing prices for a product, model or category over time.
  • Inventory sourcing - spot popular products and price gaps between sourcing and resale.
  • Category research - compare demand and price distribution across brands, models and conditions.
  • Repricing workflows - feed sold-price evidence into a marketplace repricing or valuation model.
  • Auction and estate research - document recent sale evidence for collectibles, electronics and parts.
  • AI market research - give an LLM compact comp rows with item IDs and source timestamps.

How It Works

eBay completed listings and public feedback comps becoming structured sold-price evidence rows

Provide a keyword, one or more eBay search result URLs in startUrls, or both. count caps the number of rows requested per search or URL and defaults to 20. Residential proxy configuration is strongly recommended because eBay applies aggressive bot checks to datacenter traffic.

The Actor tries the sold and completed search surface. When eBay serves a normal result page, listing rows carry item identity, price, currency, shipping, total cost and category path when those fields are available. Optional condition, seller name and end date may also appear depending on the page layout.

When the search page is walled, the Actor records a WEB_PROBE_LOG row with the candidate URL, HTTP code, wall flag and a short page snippet. It can then fall back to public buyer feedback comps, which produce FEEDBACK_COMP rows with item ID, title, sold price, currency, price text, sale-date text, seller label, relevance and source.

The two row types are intentionally distinguishable by type. A feedback comp is evidence from a public feedback profile, not a full listing record; it usually lacks shipping, condition and category path. Filter on type before aggregation, and do not compare a probe row with a sold comp. Every saved dataset row is a billable result.

Input

The Actor accepts a keyword or search URLs. The count, keyword and proxy fields are the practical controls.

FieldTypeRequiredDefaultWhat it does
startUrlsstring[]NoNoneeBay search result or marketplace URLs to process.
keywordstringNortx 4080Product or search phrase used to build an eBay sold search.
countintegerNo20Maximum rows requested per search or URL.
proxyobjectNoResidential Apify ProxyProxy configuration. Residential proxies are recommended for eBay.

Start with a narrow keyword and a small count to see which surface eBay serves. If the run returns a probe row, try a direct search URL from the marketplace you need, rotate residential proxy sessions, or run again later. A successful fallback still returns useful comps, but it is not the same as a full completed-listing page.

Output

Rows are one of two types. Sold-listing rows emphasize price, shipping and listing metadata; feedback-comp rows emphasize item identity and public sale evidence.

Field groupFieldsWhat you get
Row typetype, sourceWEB_PROBE_LOG for a blocked search attempt, FEEDBACK_COMP for a public feedback comp, or a normal listing row when search succeeds.
Comp identityitemId, title, url, keywordeBay item ID, listing title, item URL and the search phrase that produced the row.
PricesoldPrice, soldCurrency, priceText, soldDateTextSold price, currency, displayed price text and the sale-date label from the source.
Listing costsshippingPrice, totalPriceShipping and total cost when a full listing row exposes them. These are often absent on feedback comps.
Sellerseller, sellerName, verifiedPurchasePublic seller or buyer label and a verified-purchase flag when available.
DiagnosticsprobeLogProbe attempts with candidate URL, strategy, HTTP code, wall flag, byte count and a short snippet.
SourcescrapedAtObservation timestamp for the row.

A FEEDBACK_COMP row does not include shipping, condition or category path, so do not fill those fields with zero or guesswork. soldPrice is a string; parse it after checking soldCurrency. A WEB_PROBE_LOG row is diagnostic and should be excluded from price statistics. If eBay returns a login, CAPTCHA or error page, the Actor does not store that page as a sold item.

Pricing

Pricing is pay-per-event. A start event is charged per run and each dataset row is charged as a result.

EventFREEBRONZESILVERGOLD+
Actor start, per run$0.00005$0.00005$0.00005$0.00005
Dataset row$0.0025$0.0025$0.0025$0.0025

That is $2.50 per 1,000 rows, so a 20-row test costs about $0.05 before the start fee. Diagnostic probe rows are still dataset rows and should be budgeted for. There is no separate free-preview promise in the current build; set count deliberately and filter diagnostic rows after export.

Example Input

{
"keyword": "rtx 4080",
"count": 10,
"proxy": {
"useApifyProxy": true,
"apifyProxyGroups": [
"RESIDENTIAL"
]
}
}

This requests up to ten rows for a completed RTX 4080 search and explicitly prefers residential proxy. If eBay walls the search, expect a probe row plus feedback comps rather than a full listing set.

Example Output

{
"type": "FEEDBACK_COMP",
"itemId": "227370375951",
"title": "Gigabyte RTX 4080 SUPER Windforce V2 16GB GDDR6X - Tested Working",
"soldPrice": "824.95",
"soldCurrency": "US",
"priceText": "US $824.95",
"soldDateText": "Past 6 months",
"seller": "eBay automated feedback",
"relevance": 2,
"source": "feedback_profile",
"keyword": "rtx 4080",
"url": "https://www.ebay.com/itm/227370375951",
"scrapedAt": "2026-10-18T15:44:37.849Z"
}

This is a real fallback row from a run where the search surface was walled. It is useful sold-price evidence, but it has no shipping, condition or category path. A normal listing row would include those fields when eBay exposes them.

Integrations and Automation

Call the Actor through the Apify API, Apify MCP, a schedule, Zapier, Make or n8n. Export JSON, CSV or Excel, or push rows to Google Sheets, Airtable, a pricing database or a webhook.

For comps, filter to rows where type is a comp or listing, group by normalized title or model, and keep soldDateText as a coarse recency label. Do not mix probe rows into averages. If you need shipping-adjusted totals, use only rows where shippingPrice or totalPrice is present.

For recurring price tracking, store itemId, soldPrice, soldCurrency and scrapedAt on every run. Because sold listings and feedback comps can overlap, deduplicate on item ID before calculating a median or trend.

FAQ

Does it always return full completed listings?

No. eBay can wall the search surface. The current build may return a diagnostic probe row and public feedback comps instead. Check type before using the data.

What is a FEEDBACK_COMP row?

A sold-price record derived from a public eBay buyer feedback profile. It carries item ID, title, price, currency and sale-date text, but usually lacks shipping, condition and category details.

Why is shippingPrice missing?

Shipping and total cost are only available when a full listing row exposes them. Feedback comps and walled runs often omit those fields. Do not substitute zero.

Do I need an eBay API key?

No. The Actor reads public pages and does not require an eBay developer account or API key.

Can I use search URLs from another eBay marketplace?

Yes. Paste the marketplace search URL in startUrls. Item-level results still depend on what eBay serves to the request.

What should I do if I only get a probe row?

Try a narrower keyword, a direct marketplace search URL, fresh residential proxy sessions, or a later run. A probe row documents a wall; it is not a sold-price result.

For AI Agents and LLM Apps

The Actor provides item-level sold-price evidence with a row-type discriminator, source timestamps and optional diagnostic records. It is suitable for resale comps and pricing agents through the Apify API or Apify MCP.

  • Filter on type first. WEB_PROBE_LOG rows are diagnostics, not price observations.
  • FEEDBACK_COMP rows usually lack shipping and condition. Preserve nulls instead of imputing values.
  • soldPrice is a string. Parse it with soldCurrency and keep the original priceText for audit.
  • Deduplicate on itemId when combining sold listings and feedback comps.
  • Every saved row, including a diagnostic row, is billed as a dataset result.

This Actor is an independent tool and is not affiliated with, endorsed by or sponsored by eBay. It reads publicly available listing and feedback data for resale research, price analysis and inventory decisions. eBay terms and applicable law still apply.

Sold prices are observations, not appraisals or guarantees. Item titles, images and descriptions may be protected by third-party rights. Do not use the Actor to circumvent access controls, scrape private account data or republish eBay content in violation of its terms.

SEO Keywords

eBay sold items scraper, eBay scraper, eBay price tracker, eBay completed listings, eBay sold prices, eBay resale comps, eBay market data, eBay API alternative, sold listing data, eBay item prices, resale price research, eBay feedback comps, eBay product research, price monitoring, eBay dataset, completed listing scraper, eBay auction data, eBay comps tool, resale market analysis, eBay sold search