Ebay Seller Scraper

eBay Seller Scraper — Feedback Score, Listings and Prices

eBay Seller Scraper pulls public storefront data for any eBay seller — store name, feedback score, and every live listing's title and price — and returns it as structured JSON ready to use. Paste a seller's profile or store URL and get a clean dataset row per seller, no eBay account, browser, or manual copy-pasting required. Run it on Apify now to see your first seller's listings in minutes.

What is eBay Seller Scraper?

eBay Seller Scraper is an Apify Actor that visits a seller's public eBay storefront page and extracts their store name, feedback score, and currently listed items with titles and prices, returning one JSON row per seller. It works from plain HTTP requests to the public page — no eBay account, login, or session cookie is used or required. It's built for resellers, market researchers, and developers who need seller-level eBay data on a schedule without maintaining their own scraping code.

What eBay seller data is publicly available to scrape?

Anyone who opens a seller's storefront page on eBay — no account required — can see their store name, feedback percentage, and current live listings with prices. Other details about a seller are either not exposed on the storefront at all or require being logged in to view.

Data Category	Publicly Available	Restricted behind [gate]
Seller/store name	Yes	—
Storefront URL	Yes	—
Feedback percentage score	Yes	—
Active listing titles	Yes	—
Active listing prices	Yes	—
Detailed feedback comments left by buyers	No	eBay login required to browse the full feedback log
Contacting the seller	No	Requires a buyer eBay account login
Sold/completed listing history	No	Requires a logged-in eBay session with completed-items filters

eBay Seller Scraper only returns publicly visible data — what any visitor sees. Nothing behind a login wall.

What data can I extract with eBay Seller Scraper?

eBay Seller Scraper returns seller identity, feedback, and live listing data in one flat JSON row per seller, plus a scrape timestamp.

Field Name	Description
url	The seller's canonical storefront URL (/usr/<user> or /str/<user>)
name	The seller's store or username as shown on the storefront
feedback_score	The seller's public feedback percentage (e.g. "100%")
listings	Array of the seller's currently live listings, each with title and price
listings[].title	Title text of an individual live listing
listings[].price	Displayed price of that listing, with currency symbol
scrapedAt	ISO-8601 UTC timestamp of when the row was collected

Seller identity fields

url, name — identify and link back to the exact storefront that was scraped.

Feedback & reputation

feedback_score — the seller's public reputation signal, pulled straight from their storefront feedback link.

Live listings & timestamps

listings (with nested title and price per item) and scrapedAt — what the seller currently has for sale, and when that snapshot was taken.

🤖 Add-on: Need additional eBay data?

If you need full product-level detail rather than seller-level snapshots — images, item numbers, item location, brand, category, sold counts — pair this Actor with eBay Product Scraper (Scraper-Engine/eBay-Scraper), which scrapes individual eBay listing and search-result pages. Feed the listing links this Actor surfaces straight into it for deeper per-item data.

How does eBay Seller Scraper differ from the official eBay API?

eBay publishes official developer APIs (Browse API, Finding API, Trading API) that require a registered developer application, OAuth authentication, and eBay's approval before production use, whereas eBay Seller Scraper runs immediately from a public storefront URL with no eBay credentials at all.

Feature	Official eBay APIs	eBay Seller Scraper
Access requirement	Registered developer app + OAuth token	Just a seller profile or store URL
Approval process	Application review by eBay	None — runs immediately on Apify
Rate limits	Tiered call quotas set by eBay per application	Governed by your Apify run and proxy setup, not an eBay-imposed API quota
Data scope	Structured catalog access scoped to your app's granted permissions	Whatever is visible on the seller's public storefront page
Setup time	Developer account, app keys, OAuth flow before first call	Paste a URL and click Start
Output consistency	Follows eBay's official API schema versioning	Stable Actor-defined schema regardless of eBay's page markup changes

Use the official API when you already hold developer credentials and need deep, permissioned catalog integration inside your own application. Use eBay Seller Scraper when you want fast, credential-free access to what a specific seller's storefront shows right now.

How to use eBay Seller Scraper

eBay Seller Scraper runs on Apify like any other Actor — no separate signup or API key is needed to start a run.

1. Open eBay Seller Scraper's page on the Apify Store and click Try for free / Start.
2. Paste one or more seller storefront URLs into the required urls field (e.g. https://www.ebay.co.uk/usr/chrisjoh7639).
3. Optionally open proxyConfiguration to enable Apify Proxy — normal runs can leave this on No proxy.
4. Click Start to launch the run.
5. Open the Output tab once finished, or download results as JSON or CSV.

How to scale to bulk eBay seller extraction

The urls field is a list — add as many seller profile or store links as you need, one per line, in a single run. The Actor processes them one at a time in that same run, automatically escalating from a direct request to Apify's Datacenter and then Residential proxy groups per seller if it gets blocked. There's no separate "bulk mode" input; scaling up simply means adding more lines to urls.

What can you do with eBay seller data?

• A dropshipping researcher tracking competitor storefronts uses listings (title/price pairs) alongside repeated scrapedAt snapshots to spot price changes on watched sellers over time.
• A reseller vetting potential suppliers uses feedback_score together with listings[].price to judge a seller's reliability before reaching out.
• A marketplace analyst building a seller watchlist uses url and name to de-duplicate sellers tracked across multiple runs.
• A brand-protection team scanning for suspicious resale activity uses listings[].title to flag sellers whose listing names match protected keywords.
• An AI engineer building a RAG pipeline over competitor sellers feeds the name, feedback_score, and listings JSON directly into a vector store, letting an agent answer questions like "which watched sellers changed prices this week" without any manual data cleanup.

How does eBay Seller Scraper handle rate limits and blocking?

Each run starts with a direct, unproxied request per seller (after a quick unproxied probe to detect whether that seller uses a /usr/ or /str/ storefront). A random 1–2 second delay is added before every request to avoid firing requests in a burst. If a response comes back blocked — HTTP 403/429/503, an empty body, or the text of eBay's "Pardon Our Interruption" challenge page — the Actor escalates that seller to an Apify Datacenter proxy group, and if still blocked, to a Residential proxy group, retrying up to three times with a fresh session each time. Proxy session IDs are sanitized per seller so escalation doesn't silently fail. If a seller is still blocked after all retries, that seller is skipped with a warning in the log and does not appear in Output — the run itself keeps going for the remaining sellers rather than failing outright.

⬇️ Input

Parameter	Required	Type	Description	Example Value
urls	Yes	array	One or more eBay seller profile or store URLs, one per line. Accepts /usr/<username>, /str/<storename>, or legacy _ssn=<username> links.	https://www.ebay.co.uk/usr/chrisjoh7639
proxyConfiguration	No	object	Apify Proxy configuration. Defaults to no proxy; the Actor automatically escalates to Datacenter, then Residential proxy groups on its own if a request is blocked.	{ "useApifyProxy": false }

Example input

{
  "urls": [
    "https://www.ebay.co.uk/usr/chrisjoh7639",
    "https://www.ebay.co.uk/str/somestorefront"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

⬆️ Output

Each run writes one JSON row per successfully scraped seller to the Actor's dataset, exportable as JSON, CSV, Excel, or the other formats Apify's dataset export supports. Only sellers the Actor could actually fetch and parse are billed and written — a blocked or unparseable seller is skipped and never appears as a partial row.

Example output

{
  "url": "https://www.ebay.co.uk/usr/chrisjoh7639",
  "name": "chrisjoh7639",
  "feedback_score": "100%",
  "listings": [
    { "title": "Vintage Leica M6 35mm Film Camera Body", "price": "£450.00" },
    { "title": "Canon EF 50mm f/1.8 STM Lens", "price": "£85.00" }
  ],
  "scrapedAt": "2026-07-25T09:14:32.118203+00:00"
}

How does it work?

eBay Seller Scraper fetches each seller's canonical storefront page (/usr/<user> for individual sellers, /str/<user> for eBay Store sellers, auto-detected per seller with a quick probe) using plain HTTP requests carrying real-browser headers — no login or session cookie involved. If eBay's bot defenses return a blocked or challenge response, the Actor retries the same request through Apify's Datacenter and then Residential proxy groups before giving up on that seller. The page is parsed with BeautifulSoup against eBay's current storefront markup, with older selector patterns kept as fallbacks so extraction keeps working even if eBay serves a different page layout. Only what's visible to any ordinary visitor is extracted, and the output's field names stay the same regardless of how eBay's page design changes underneath.

Integrations

eBay Seller Scraper works wherever you can make an HTTP call or run an Apify Actor — no eBay-specific SDK required.

Calling eBay Seller Scraper programmatically

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run = client.actor("ebay-seller-scraper").call(run_input={
    "urls": ["https://www.ebay.co.uk/usr/chrisjoh7639"],
    "proxyConfiguration": {"useApifyProxy": False},
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Works in Go, Ruby, Node.js, cURL — any language that can make an HTTP request.

MCP integration for AI agents

eBay Seller Scraper is reachable through Apify's Actors MCP Server, which exposes any Apify Actor as a callable MCP tool. Register it by running npx -y @apify/actors-mcp-server --actors ebay-seller-scraper (with your APIFY_TOKEN set) and connect it as an MCP server in Claude Desktop, Claude Code, or any other MCP-compatible client — the Actor then appears as a tool the agent can call with the urls input directly.

No-code tools (n8n, Make, LangChain)

In n8n, use the HTTP Request node pointed at Apify's run-sync-get-dataset-items endpoint for this Actor, passing your urls input as the request body. In Make, use the Apify app's "Run Actor and get dataset items" module and map the seller URLs into its input field. In LangChain, load results through the Apify dataset loader after a run completes, and pass each row's listings and feedback_score into your chain as document metadata.

Is it legal to scrape eBay seller data?

Scraping publicly available eBay seller storefront data — the kind visible to any visitor without logging in — is generally permissible, though eBay's own Terms of Service place restrictions on automated access, so use is at your own discretion. eBay Seller Scraper only returns publicly available data: a seller's store name, feedback score, and current listing titles and prices, all of which is business/marketplace data rather than personal data about an individual, since no buyer information or personal contact details are collected. Consult legal counsel if your use case involves bulk storage of this data or scraping at a scale that could raise ToS or database-rights concerns.

Frequently asked questions

What eBay seller fields does eBay Seller Scraper return?

It returns name, feedback_score, listings[].title, listings[].price, and scrapedAt per seller, plus the seller's url. See What data can I extract above for the full field list.

Does eBay Seller Scraper require an eBay account or login?

No. It fetches each seller's public storefront page over plain HTTP with no cookies or session — no eBay account, password, or login of any kind is used.

How many eBay sellers can I extract in one run?

There's no fixed cap in the input schema — urls accepts as many seller links as you add, and the Actor processes them one at a time within that run.

What happens if a seller's page is blocked, missing, or has no listings?

If a URL can't be parsed into a valid seller username, that entry is skipped with a warning and never sent to Output. If the page loads but is blocked by eBay's anti-bot defenses even after proxy escalation, that seller is also skipped rather than added as an empty or broken row — the rest of the run continues normally.

Can I scrape multiple eBay sellers at once?

Yes. Add each seller's storefront URL as its own line in the urls array and they're all processed within a single run.

Does eBay Seller Scraper work with Claude, ChatGPT, and other AI agent tools?

Yes. It's callable as a standard HTTP API by any agent framework, and reachable through Apify's Actors MCP server for MCP-compatible clients such as Claude.

How does eBay Seller Scraper compare to checking eBay storefronts manually?

It automates what you'd otherwise do by opening each seller's storefront in a browser and copying the feedback score and listing titles/prices by hand — one run processes an entire list of seller URLs and returns structured JSON instead of manual notes.

Does eBay Seller Scraper return data in a format LLMs can use directly?

Yes. Output is typed, normalized JSON with consistent field names across runs — no HTML parsing or CSS selectors needed. Pass it directly to an LLM, index it in a vector store, or feed it to an agent tool.

What happens when eBay changes its storefront layout or anti-bot system?

The Actor's parser is built with fallback selector chains — it tries the current storefront markup first, then two older card layouts, so the output schema keeps working even if eBay changes its page design. No specific fix turnaround time is promised.

Can I use eBay Seller Scraper without managing proxies or browser infrastructure?

Yes. The Actor tries a direct request first and automatically escalates through Apify's Datacenter and Residential proxy groups on its own if blocked — you don't need to configure or rotate proxies yourself, though the proxyConfiguration input lets you tune this if you want to.

Which eBay seller fields work best for AI training data and RAG indexing?

listings[].title is the highest-information text field for RAG indexing. feedback_score, listings[].price, and scrapedAt are consistently structured across every record, making them well suited to training data pipelines — all fields return as typed primitives (strings and arrays), with no HTML to strip.

Related scrapers

Scraper Name	What it extracts
eBay Product Scraper	Full per-listing detail from eBay search and item pages — price, images, seller, brand, category, and more
Amazon Seller Data Extractor: AI Sentiment & Feedback Analytics	Amazon seller storefront data with AI-powered feedback sentiment analysis
Amazon Best Sellers Scraper	Ranked Amazon best-seller products by category
Facebook Marketplace Scraper	Marketplace listings collected from Facebook Marketplace search links

Your feedback

Found a bug or missing a field? Let us know through this Actor's Issues tab on Apify so we can take a look. Feedback like this directly shapes what gets fixed and added next.