eBay Product Listing Scraper With Seller Feedback

eBay Scraper — Extract Listings, Buyer Feedback & Seller Data

eBay Product Listing Scraper With Seller Feedback pulls live product listings from any eBay.com search or category URL — title, price, condition, shipping, images — and, opt-in, follows each listing to its own item page to collect buyer feedback and seller reputation data too. Every run returns typed, normalized JSON: listing rows, linked buyer-feedback rows, and seller-reputation fields (feedback score, positive-feedback %, items sold) — no HTML, no selectors, no parsing. Read on for the full input schema, every output field, and how this compares to eBay's own Browse API.

🧭 What is eBay Product Listing Scraper With Seller Feedback?

eBay Product Listing Scraper With Seller Feedback is an Apify Actor that scrapes eBay.com search-result and category pages and returns structured JSON for every listing found — no eBay account or login is required, since it only reads pages that are publicly visible to any visitor. On top of the base listing extraction it adds two opt-in enrichment steps that visit each listing's own item page:

• Scrape eBay listings — title, price, condition, images, shipping, location, buying format, returns policy
• Scrape buyer feedback for a listing — reviewer, rating type, comment, date range, photo count
• Scrape seller reputation for a listing — positive-feedback %, items sold, username, lifetime feedback score
• Export results as JSON, CSV, Excel, or any other format the Apify dataset export supports
• No proxy management — the Actor escalates through connection tiers automatically

📋 What data does eBay Product Listing Scraper With Seller Feedback collect?

The Actor returns three kinds of data in one run: the listing itself, its buyer feedback (when requested), and its seller's reputation (when requested).

Data Type	Key Fields	JSON Field Names
Listings	title, price, condition, image, shipping, location, buying format, returns	product_title, price, original_price, condition, image_url, shippingCost, itemLocation, buyingFormat, returnsAccepted
Buyer feedback	reviewer, rating, comment, date range, photos	reviewerName, ratingType, comment, dateRange, photoCount
Seller reputation	username, positive-feedback %, items sold, feedback score	sellerUsername, sellerPositiveFeedbackPct, sellerItemsSold, sellerFeedbackScore

Need more eBay data?

This Actor is built for listing plus reputation data from live search and category pages. If you need sold/completed-listing history or a different eBay page type, check this publisher's other Apify Store listings for a dedicated tool before writing a custom scraper.

📡 How does eBay Product Listing Scraper With Seller Feedback differ from the official eBay API?

eBay's own Browse API returns per-item and per-search JSON to registered developer applications; this Actor returns the same categories of data — plus buyer feedback comments the Browse API doesn't expose — from a pasted URL, with no app registration.

Feature	eBay Browse API (official)	eBay Product Listing Scraper With Seller Feedback
Access & setup	Register an eBay Developer Program application and generate an OAuth token before your first call	Paste search/listing URLs and run — no eBay account or API key
Daily call limit	Standard limit of 5,000 calls/day per application, raisable via an "Application Growth Check" request (developer.ebay.com, checked 2026-08-15)	No platform-imposed daily call cap coded into the Actor's listing-scraping path (the buyer-feedback/seller-profile enrichment step is capped internally — see "How many results")
Individual buyer feedback comments	Not returned by the Item resource; individual feedback records require the separate, older Trading API's GetFeedback call, scoped to a seller account rather than a listing (developer.ebay.com, checked 2026-08-15)	Returned directly as feedback rows (reviewerName, ratingType, comment, dateRange, photoCount) linked to the listing by itemId, opt-in via fetchBuyerFeedback
Seller reputation fields	feedbackScore and feedbackPercentage are returned on the Item resource's seller object (developer.ebay.com, checked 2026-08-15)	The same two figures (sellerFeedbackScore, sellerPositiveFeedbackPct) plus sellerItemsSold, opt-in via fetchSellerProfile
Output shape	Endpoint-specific JSON, one call per item or search	One flat JSON row per listing (and per feedback entry), ready for direct dataset export
Setup time	Application registration and, for higher limits, a growth-check review	Running within minutes of opening the Actor

The Browse API is the right choice for a production integration that can register an application and operate under (or negotiate past) its daily call limit. This Actor is the right choice for ad hoc or bulk research — competitor price checks, seller due diligence, feedback audits — where listing, buyer-feedback, and seller-reputation data together in one pass matters more than a formal API contract.

🎯 Why do developers and teams scrape eBay?

• For AI engineers and agent builders — feed listing and seller-reputation data straight into a pricing or sourcing agent. A tool call that returns price, sellerFeedbackScore, and sellerPositiveFeedbackPct for a search query lets an agent rank suppliers by trust and cost without a separate lookup step, and the typed JSON drops straight into a RAG index or agent tool schema.

• For dropshippers and resellers — check sellerPositiveFeedbackPct and sellerItemsSold before sourcing stock from a seller, and monitor price and original_price across a category to spot markdowns worth reselling.

• For pricing and market analysts — pull price, condition, and shippingCost across many search URLs in one run to track how a product category is priced and shipped, without visiting eBay by hand.

• For trust and due-diligence researchers — read actual buyer comment and ratingType text for a listing's seller, filtered to Positive, Neutral, or Negative, to spot patterns a raw feedback score alone doesn't show.

🚀 How to scrape eBay (step by step)

1. Open eBay Product Listing Scraper With Seller Feedback on its Apify Store listing and click Try for free (or Run, if already added to your account).
2. Paste one or more eBay search or category URLs into sourceUrls — no field is required by the schema, but the run fails without at least one URL.
3. Turn on fetchBuyerFeedback and/or fetchSellerProfile if you need reputation data, and set feedbackRatingFilter / maxFeedbackPerListing to shape what's collected.
4. Click Start. Watch the Log tab for per-page progress.
5. Download results as JSON or CSV from the Dataset tab, or pull them via the Apify API.

What to do when eBay changes its structure

The Actor is maintained and its output schema is designed to stay stable, so field names and types don't change on your end even after the extraction logic underneath is updated to match a page change. No specific turnaround time is promised for any given break.

⬇️ Input

Parameter	Required	Type	Description	Example Value
sourceUrls	No	array	eBay search or category URLs to scrape.	["https://www.ebay.com/sch/260010/i.html?_nkw=shoe&Brand=Nike"]
urls	No	array	Legacy alias of sourceUrls, kept for backward compatibility with the base eBay Product Listing Scraper's input shape. Used only when sourceUrls is empty.	[]
fetchBuyerFeedback	No	boolean	When true, visits each listing's own product page and collects its buyer feedback/reviews as separate rows, linked back to the listing by itemId. Default: false.	true
feedbackRatingFilter	No	string (enum: All, Positive, Neutral, Negative)	Only used when fetchBuyerFeedback is on. Restricts collected feedback rows to a rating type. Default: All.	"Positive"
maxFeedbackPerListing	No	integer (min 0)	Caps how many buyer feedback rows are collected per listing when fetchBuyerFeedback is on. 0 = no limit. Default: 10.	10
fetchSellerProfile	No	boolean	When true, looks up each listing's seller profile once per run (deduplicated across listings from the same seller) to add sellerFeedbackScore. Default: false.	true
proxyConfiguration	No	object	Optional. Leave default (no proxy) for most runs — the Actor escalates through fallback connection options automatically. Set useApifyProxy: true to apply your own configuration from the first request.	{ "useApifyProxy": false }

No parameter is required at the schema level, but the run fails with Missing required input: sourceUrls/urls if both sourceUrls and the legacy urls are empty.

Example input:

{
  "sourceUrls": ["https://www.ebay.com/sch/260010/i.html?_nkw=shoe&Brand=Nike"],
  "urls": [],
  "fetchBuyerFeedback": true,
  "feedbackRatingFilter": "All",
  "maxFeedbackPerListing": 10,
  "fetchSellerProfile": true,
  "proxyConfiguration": { "useApifyProxy": false }
}

Common pitfall: leaving fetchBuyerFeedback and fetchSellerProfile both off returns listing rows only, with the reputation fields present but null — turn on the toggle for the data you actually need.

⬆️ Output

Every run pushes typed JSON rows to the default dataset — one row per listing, plus one extra row per collected buyer-feedback entry when fetchBuyerFeedback is on. Export as JSON, CSV, Excel, or any format the Apify dataset export supports.

Scraped listing

{
  "itemId": "123456789012",
  "product_title": "Nike Air Max 270 Men's Running Shoes",
  "condition": "New with box",
  "price": "$89.99",
  "image_url": "https://i.ebayimg.com/images/g/abcAAOSw.../s-l1600.jpg",
  "original_price": "$120.00",
  "shippingCost": "+$8.99 delivery",
  "itemLocation": "Located in United States",
  "buyingFormat": "Buy It Now",
  "returnsAccepted": "30 days returns",
  "card_attribute": ["Buy It Now", "+$8.99 delivery", "Located in United States", "30 days returns"],
  "product_url": "https://www.ebay.com/itm/123456789012",
  "input_url": "https://www.ebay.com/sch/260010/i.html?_nkw=shoe&Brand=Nike",
  "sellerPositiveFeedbackPct": "98.5% positive",
  "sellerItemsSold": "2.4K",
  "sellerUsername": "shoe_outlet_2024",
  "sellerFeedbackScore": "18,204",
  "scrapedAt": "2026-08-15T10:12:03Z",
  "type": "listing",
  "isChild": false
}

sellerPositiveFeedbackPct, sellerItemsSold, and sellerUsername are populated whenever fetchBuyerFeedback or fetchSellerProfile is on (they come free with the same item-page fetch); sellerFeedbackScore is populated only when fetchSellerProfile is on. All four are present and null when neither toggle is used.

Scraped buyer feedback

{
  "type": "feedback",
  "isChild": true,
  "itemId": "123456789012",
  "reviewerName": "b***r (214)",
  "ratingType": "Positive feedback rating",
  "comment": "Exactly as described, fast shipping, would buy again.",
  "dateRange": "Past 6 months",
  "photoCount": 2,
  "scrapedAt": "2026-08-15T10:12:05Z"
}

Feedback rows are pushed to the default dataset alongside listing rows (filter on type to separate them), and are also mirrored to a per-run dataset named <runId>-buyer-feedback for convenience.

🆚 How does eBay Product Listing Scraper With Seller Feedback compare to other eBay scrapers?

Feature	eBay Product Listing Scraper With Seller Feedback	Generic eBay scraper
Output format	Typed JSON with stable field names ✅	Often raw HTML or inconsistent JSON that needs custom parsing ❌
Buyer feedback per listing	Reviewer, rating type, comment, date range, and photo count, linked by itemId ✅	Not commonly offered ❌
Seller reputation per listing	Feedback score, positive %, and items sold, deduplicated per seller across a run ✅	Not commonly offered ❌
High-resolution images	Image URLs upgraded to eBay's real maximum-resolution token ✅	Often left at the thumbnail size returned by the page ❌
Proxy/anti-bot handling	Automatic escalation across connection tiers with a soft-block content check, not just an HTTP status check ✅	Frequently left for the user to configure ❌

If you're building an AI agent or RAG pipeline, the output-format row is the decision-maker — parsing HTML inside an agent loop is a reliability failure mode, not a feature.

🔢 How many results can you scrape with eBay Product Listing Scraper With Seller Feedback?

There is no maxItems-style cap on listings themselves — every listing found on each fetched page is returned, and the schema places no ceiling on how many sourceUrls you can supply. ⚠️ The Actor does not auto-paginate a single eBay search beyond the page you give it: each URL is fetched once, so to cover more than one page of results, paste each page's URL (eBay's own _pgn parameter, for example) into sourceUrls. ⚠️ Separately, the buyer-feedback/seller-profile enrichment step is capped at the first 25 listings encountered in a run — every listing is still returned, but listings beyond that count get blank reputation fields and no feedback rows even with the toggles on. No benchmark run time is published; actual duration depends on how many URLs and enrichment fetches a run makes.

🔌 Integrate eBay Product Listing Scraper With Seller Feedback and automate your workflow

eBay Product Listing Scraper With Seller Feedback works with any language or tool that can send an HTTP request.

REST API integration

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_API_TOKEN>")
run = client.actor("<YOUR_USERNAME>/ebay-product-listing-scraper-with-seller-feedback").call(
    run_input={
        "sourceUrls": ["https://www.ebay.com/sch/260010/i.html?_nkw=shoe&Brand=Nike"],
        "fetchBuyerFeedback": True,
        "fetchSellerProfile": True,
    }
)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["type"], item.get("product_title") or item.get("reviewerName"), item.get("price"))

Works in Python, Node.js, Go, Ruby, cURL — anything that can call the Apify API.

Automation platforms (n8n, Make, LangChain)

Apify publishes an official node for n8n and an official app for Make — either can run this Actor on a schedule and pass its dataset into a downstream workflow step. For LangChain-based agents, Apify's own integration exposes Actors as callable tools, so a sourcing or pricing agent can invoke this Actor and read its dataset without a custom HTTP wrapper.

⚖️ Is it legal to scrape eBay?

Yes — scraping publicly available listing data is generally lawful, and eBay Product Listing Scraper With Seller Feedback only fetches eBay pages visible to any visitor without logging in. The core output — listings, prices, shipping, and seller reputation figures — is business and product data, not personal data, so GDPR's rules on personal-data processing do not attach to it; what applies instead is eBay's own Terms of Service governing automated access, and database-rights law in some jurisdictions protecting the compiled catalog. The optional buyer-feedback rows do include a reviewerName string tied to individual comments, which can qualify as personal data in some jurisdictions if the underlying eBay username is linked to an identifiable person — treat that add-on with the same care as any reviewer/commenter dataset. Consult legal counsel for commercial use cases involving bulk personal data.

❓ Frequently asked questions

Does eBay Product Listing Scraper With Seller Feedback work without an eBay account?

Yes. No eBay login or account is required — the Actor only reads search, category, and item pages that are public to any visitor.

How often is the scraped data updated?

Every run fetches eBay's pages live at the time it runs; nothing is served from a cache. Prices, feedback, and reputation figures reflect what eBay showed at the moment of the run.

What happens if a listing has no buyer feedback or its seller has no visible feedback score?

The run doesn't fail. If a listing's item page has no feedback entries, fetchBuyerFeedback simply produces zero feedback rows for it. Seller feedback score coverage is limited to sellers whose profile page renders a store-style header widget; a lower-volume seller's profile can genuinely omit any numeric score, in which case sellerFeedbackScore is returned as null rather than guessed.

Can I scrape private or restricted eBay content?

No. Only publicly accessible search, category, item, and seller-profile pages are read — nothing behind an eBay account login.

What does it cost to run this Actor?

The Actor uses Apify's Pay-Per-Event pricing, charging a single row_result event for every row pushed to the dataset — listing rows and buyer-feedback rows alike. Current pricing is shown on the Actor's Apify Store page before you start a run.

Does eBay Product Listing Scraper With Seller Feedback work for AI agent workflows and LLM pipelines?

Yes. It's callable as an HTTP endpoint by any agent framework through the Apify API — every response is typed JSON with stable field names, ready to pass to an LLM context window or route through an agent tool without a parsing step.

How does eBay Product Listing Scraper With Seller Feedback handle eBay's anti-bot system?

Each request escalates through connection tiers (no proxy, then datacenter, then residential) and checks the returned page for real listing content — at least three item links — rather than trusting an HTTP 200 alone, since a soft-block or sign-in shell page can return 200 with no data. Once a tier succeeds, that connection is reused (sticky) for the rest of the run. Item-detail, feedback, and seller-profile fetches use a separately warmed, IP-pinned session so eBay's per-IP anti-bot clearance isn't lost between requests.

Does eBay Product Listing Scraper With Seller Feedback return data in a format LLMs can use directly?

Yes. Typed, normalized JSON with stable field names — no HTML, no selectors, no parsing — so it can be indexed into a vector store or passed straight into an LLM prompt.

Can I use eBay Product Listing Scraper With Seller Feedback without managing proxies?

Yes. Leave proxyConfiguration at its default and the Actor escalates through connection tiers automatically. Set useApifyProxy: true only if you want your own proxy configuration applied from the first request.

What happens when eBay changes its structure or blocks the scraper?

The Actor is maintained and its output schema is designed to stay stable, so field names and types don't change on your end. No numeric turnaround time is promised for any given fix.

💬 Your feedback

Found a bug, or need a field this Actor doesn't return yet? We want to know. Use the Issues tab or the "Contact developer" button on this Actor's Apify Store page to report it — that's the fastest way to get a fix or a new field considered.