eBay Scraper — Search & Item Details | $3.4/1K

eBay Scraper — Search & Item Details

Built for e-commerce analysts, resale arbitrage traders, and price intelligence tools that need clean eBay data without OAuth apps or proxy subscriptions.

Pricing: Pay per listing — $1.50/1K (search results), $3.00/1K (item detail mode with full metadata). First 10 results free.

No eBay API key needed. No login. No proxy required.

Scrape eBay search results and item detail pages into clean, structured JSON.

What you get

Search mode (searchQueries): scrape listing cards from eBay search results.

Field	Description
item_id	eBay numeric item ID
title	Full listing title
price	Numeric price (e.g. 334.03)
currency	Currency code (USD, EUR, GBP, ...)
condition	Condition text as shown in search card
listing_type	"Buy It Now", "Auction", "or Best Offer"
shipping	Shipping cost string (e.g. "+$9.99 delivery", "Free shipping")
seller_name	Seller username
seller_feedback	e.g. "99.5% positive (162.4K)"
location	Item location country/city
url	Canonical eBay item URL
image_url	Primary product image
source	"search"
query	The search keyword that produced this record
page	Result page number
parse_confidence	0.0–1.0 quality score
warnings	List of parser warning codes
scraped_at	ISO 8601 timestamp

Item detail mode (itemIds): fetch individual item pages for richer data.

Additional fields vs search: availability, image_urls (all images), brand, model, color.

How it works

This actor accesses eBay's public listing pages without login or credentials. No proxy is required from Apify's infrastructure as of the time of writing (probed May 2026).

Parser design: structural anchors (data-listingid, div[role="heading"], li[data-view],
schema.org JSON-LD) rather than fragile CSS class names. When eBay changes its layout,
parse_confidence drops below 0.5 — your monitoring catches it before buyers notice.

Item pages: resolved via schema.org JSON-LD Product embedded in every item page —
far more stable than HTML selectors. Falls back to HTML for fields JSON-LD doesn't cover
(seller info, location).

Access notes

• Item pages: require a warm session (fetch search first, then item). A fresh cold
  item request triggers a JS challenge; this actor handles it automatically.
• No proxy needed today — the actor runs cleanly from Apify's datacenter IPs.
  Add a residential proxy via proxyConfiguration as a fallback (paid for by the buyer).

eBay official Browse API?

eBay's official Browse API requires OAuth app credentials (developer application key) and
has strict rate limits on the free tier. This actor uses the public website instead —
no credentials, no quota, all public listing data. Buyer data / private account data
is not accessible and not scraped.

vs. competitors

Feature	This actor	apify/ebay-scraper (epctex)
Reliable access from Apify cloud	Yes	No — breaks frequently
parse_confidence drift signal	Yes	No
Detail-mode depth toggle	Yes	No
Price	$1.50/1K	$2–3/1K

parse_confidence trust signal

Every record ships a parse_confidence score (0.0–1.0). When eBay changes its layout, confidence drops below 0.5 — your pipeline catches drift before buyers notice. Low-confidence records are never silently discarded.

Use with AI agents (MCP)

This actor is tagged MCP_SERVERS — compatible with Claude, GPT-4o, and other MCP-aware agents. Point your agent at the Apify actor to pull eBay data into any LLM workflow:

https://mcp.apify.com/?tools=bovi/ebay-scraper

Inputs

Input	Type	Default	Description
searchQueries	array of strings	—	Search keywords. Each produces up to maxItems × maxPages results.
itemIds	array of strings	—	eBay item IDs for direct detail-page fetch.
maxItems	integer	200	Total records limit across all queries.
maxPages	integer	5	Pages per query (~50 results/page).
sort	string	best_match	Sort order: best_match, newest_first, price_asc, price_desc, etc.
condition	string	(all)	Filter: new, used, refurbished.
categoryId	string	—	eBay category ID to narrow scope.
minPrice / maxPrice	integer	—	Price range filter in USD.
proxyConfiguration	object	—	Optional residential proxy (not required today).

Pricing example

Volume	Mode	Cost
100 results	Search	$0.15
1,000 results	Search	$1.50
1,000 results	Item detail	$3.00
10,000 results	Search	$15.00

First 10 results are free. You pay only for items actually returned.

FAQ

Do I need an eBay API key or login? No. This actor uses the public eBay website — no credentials required.

Do I need a proxy? No proxy is needed from Apify cloud IPs as of May 2026. A proxyConfiguration input is available as a fallback — paid for by the run owner.

What output formats are available? JSON (default), CSV, and Excel — via the Apify dataset export or API.

What if results come back empty? Check your search query. eBay search returns 0 results if the keyword matches nothing, or the actor was blocked (see logs for BlockedError). Add a residential proxy via proxyConfiguration if you see 403 errors in the logs.

Legal

eBay's ToS restricts automated scraping. This actor extracts only publicly visible
listing data — the same data visible to any anonymous browser visitor. It does not
access private accounts or authentication-gated data. Use responsibly and in accordance
with applicable law. Not affiliated with eBay Inc.

Pricing

Pay-per-result: you pay only for data you receive. Priced per listing item returned.

Integrations

Built for e-commerce resellers and price-intelligence tools tracking listings, conditions, and sold prices across categories — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

Not affiliated with eBay Inc.

This is an independent tool. All eBay trademarks belong to eBay Inc.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Etsy Listings
• Facebook Marketplace Scraper
• Grailed Listings
• Kleinanzeigen Listings Scraper
• Leboncoin Listings
• Marktplaats Listings Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.