eBay listings by keyword, search URL or item URL on 10 marketplaces incl. ebay.de. One row per listing: price, shipping, condition, Buy It Now or auction, bids, units sold, watchers, seller feedback, item specifics (item pages). Free filters: condition, buying format, price range, category, sort.
1.15 — 2026-11-19 — Run cards that explain the last wait, and empty searches that say what to try
After its last listing, a run whose browser is still loading waits up to 25 s for its cookies, so your next runs need no browser; its run card now says so ("Done reading eBay: 60 listings delivered. Keeping the session that passed eBay's bot check for your next runs") instead of an old progress line.
A keyword or search URL eBay has no listing for gets a note on its status row with what to try: the spelling, a looser filter, another marketplace.
README: the first-run times measured on 2026-11-19 (one to seven browser visits, first page 32 s to 2.6 minutes) and the 1.14 runs behind the praise table.
Inputs get the same listings and charges as 1.14.
1.14 — 2026-11-19 — What other eBay scrapers' users praise: the market in a sentence, progress you can watch, clean exports, failures that say what to do
market.quick_take on every search's status row (and in SUMMARY.markets), free: the market summary in a few plain sentences, for a person or an AI agent that reads one line ("60 listings: median $19.00, middle half $10.31–$30.50 … 3 of 60 have sold (192 units), at a median $13.49 …").
The run card shows progress while the run works, every few seconds: listings so far, jobs done, eBay pages read and how eBay's bot check is going ("eBay's bot check: real-browser visit 3 on a fresh IP, 2 refused so far"). Before, it stayed blank until the end, through 30 s to 2.5 minutes of bot check on a first run.
statusRows: all (default, as before), problems (only status rows that failed, found nothing, stopped at a limit or carry a note) or none (listings only). With none a CSV export has the 43 listing columns; a full export of a run with its status row had 127, 75 of them from the market summary. SUMMARY counts every job either way, and the STATUS record lists every status row when the dataset does not.
A run eBay refused at every page still fails, and now its run card and status rows say that nothing was charged and what to do (run again: the next run starts on fresh IPs; or use Apify's RESIDENTIAL group). An empty input names the smallest one that works; a spending-limit stop says to raise the maximum cost per run.
Every dataset view names its columns in words ("Units sold", "Seller positive %"), and the Overview, the first table users see and export, carries each listing's link.
README: a Quick start (Console, one API call, AI agents), MCP setup for Claude Code, Claude Desktop, Cursor and VS Code, recipes for Google Sheets, Make, n8n, Zapier, Slack and webhooks, a table of what other scrapers' reviewers praise and how this actor measures up, and FAQ entries on speed, clean CSV exports and failed runs.
Inputs without the new field get the same listings and charges as 1.13; status rows and SUMMARY.markets have the new quick_take key, and refused jobs' status rows a note.
1.13 — 2026-11-19 — Seller feedback (add-on, not active yet) and a category redirect told apart
Seller feedback, the add-on memo23's users know: feedbackSellers (usernames or feedback-profile URLs; memo23's feedbackProfiles and /fdbk/ URLs in startUrls too) reads each seller's public feedback profile signed out, 200 entries a page, newest first or most relevant, as type = feedback rows: feedback_rating, comment, left_by (buyer, seller or eBay's automated feedback), from_user and from_user_score, when, verified_purchase, image_count, images, and the item (item_id, item_title, item_price, item_currency, item_url). maxFeedbackPerSeller, feedbackRating, feedbackReceivedAs and memo23's feedbackImagesOnly / feedbackExcludeAutomated choose what you get; entries that do not match are left out free. Billed per feedback row once its price is set; until then a run with it reads no feedback and charges nothing for it.
Fix: a keyword-less category search that eBay redirects to a category page in its other browse layout (ebay.de, _sacat=33717) is said on its status row like the other browse pages, instead of a silent "found nothing" (1.12.2: the status row had no note).
Inputs without the new fields get the same listings and charges as 1.12.
1.12 — 2026-11-19 — A free market summary for every search, caps that count what you get, category URLs, description HTML and every compatible vehicle
Every search's status row carries market, free (and SUMMARY.markets): price and landed price (price plus shipping) as min, quartiles, median, max and mean; listings and median price by condition and by buying format; units sold, the listings that have sold and their median price; watchers; the shares of auctions, Best Offer and free shipping; the top 5 sellers; the 3 cheapest listings by landed price with links. marketSummary: false turns it off; memo23's includeSummary is read as it.
Fix: with a filter checked on each card (price bounds, excludeWords phrases, freeShipping, itemLocation, minWatchers, minQuantitySold, sellerCountry, model years), maxResultsPerQuery counts the listings delivered, reading the pages allowed one at a time until it is met: 1.11 counted listings read, so 20 asked with a watcher floor gave 11 from a page that held 16. Another scraper's per-search count with such a filter, or with a title rule (memo23's maxItems with minWatchers or titleMustMatchQuery), reads on until that many pass, up to eBay's 34-page stop. Monitors still read only the pages given.
category takes an eBay category URL as well as an id: a category page (/b/…/9355/bn_…), a category search (/sch/9355/i.html) or any URL with _sacat; the URL's marketplace is used when domain is left at its default. A category alone (no keyword) is tried as a search. Fix: a /b/ category page in startUrls, which eBay answers with its merchandised browse page rather than search results, ended as a silent "found nothing"; now its status row says so and how to get the listings (add a keyword), free.
includeDescriptionHtml: item-page rows also carry description_html, the seller's own description markup, free (from the description page already read).
allCompatibleVehicles: item-page rows of parts list every vehicle the part fits, read 20 at a time through the item page's own compatibility-table paging (up to 2,000), with compatibility_complete; without it, the first 20 and the count as before.
searchInDescription: eBay's "Search including description" (LH_TitleDesc). Other scrapers' names read as ours: delicious_zebu's searchTitleDescription and splitByPrice: false, memo23's motorsCategory and includeSummary, caffein.dev's categoryId with subcategoryId (the subcategory wins).
Inputs without the new fields get the same listings and charges as 1.11; status rows and SUMMARY have the new market / markets keys.
1.11 — 2026-11-18 — Every listing of a big walk, and run cards that say only what is true
Price-band walks (above 2,040 per search) read eBay's full view, the same search with _blrs=recall_filtering that eBay's own "See more results" link opens: its default "streamlined" view showed 249 results in one $640-660 "iphone 15" band where the full view had 367. A plain search keeps eBay's default view; when eBay streamlines it, its status row and the run card say so, with the two ways to get every listing.
The run card names only pages kept as eBay priced them for a buyer abroad (SUMMARY.buyer_view.pages_priced_abroad); pages read again from the marketplace's country are counted apart (pages_read_again). 1.10 wrote "1 pages were priced by eBay for a buyer outside US" on an ebay.com run whose Vancouver-priced page (ship-to V6B2A3) had been read again from the US (run GGkec6UAW8jQvvL7V).
Inputs without the new behaviour's triggers get the same listings and charges as 1.10.
1.10 — 2026-11-18 — What other eBay scrapers' users complain about: near-matches billed, prices for the wrong country, lost big jobs, silent zeros
titleMustMatch: only listings whose title has every word of the keyword (or of a pasted search URL's keyword) are delivered; eBay's near-matches for a model number ("Line 6 Spider IV 120" also brings Spider IV 15 and Spider V 120) are left out before billing, free, and maxResultsPerQuery then counts matching listings. memo23's titleMustMatchQuery and titleMustInclude are read as ours. That exact input billed 20 near-matches on 1.9 (run njtQYO6xWW9fiAwvn) and 0 now, with "60 left out free: 60 without every search word in the title" (run w0YUVoeJJAPCoX2ah).
Fix: eBay's "Results matching fewer words" padding is never delivered, also on a page with a few exact matches (only the zero-result page was covered before): "iphone 15" between $0.01 and $0.99 had 1 match and 8 iPhone 7 Plus cards under that heading, and 1.9 billed all 9. The padding never counts toward a cap, and the page it starts on is the last one read. eBay's other notice, "We've streamlined your search results to show you the best listings", stands above real results and cuts nothing. memo23's excludeFewerWordMatches and caffein.dev's exactMatch are read (always on here).
Fix: outside the US, the run's exits are in the marketplace's own country. eBay prices every page for the visitor's country: from a US datacentre exit, ebay.co.uk showed 14 of 19 private sellers' prices £0.47-0.98 low (the Buyer Protection fee without UK VAT) and ebay.com.au lost postage on 3 of 17 rows. The datacentre pool is pinned to the country where Apify has IPs there; otherwise the run starts on residential exits in that country. Every page's ship-to code is checked, a page priced for a buyer abroad is read again from the country (or counted in SUMMARY buyer_view when nothing can fix it), and the UK fee split is never made on such a price. The same inputs now gave 16 of 16 prices equal to the UK view (run 48bVEoqE77K9UwaoQ) and 17 of 17 equal to the Australian one, none without postage (run ycrhSP9PYVY7BGAfN).
New filters, applied by eBay and checked on each card before billing: freeShipping, returnsAccepted and itemLocation (domestic / worldwide). Other scrapers' freeShippingOnly, homeCountryOnly, sellerType, aspectFilter, minWatchers, minQuantitySold, sellerCountry, keywordMatch, locatedIn, minYear/maxYear, maxItemsPerQuery and limit are read as ours instead of being ignored.
blackfalcondata's monitor input works: incrementalMode turns on onlyNew (and price changes), stateKey names the monitor's memory (it survives a filter change), emitUnchanged: true also delivers listings seen before as change = unchanged. Its query as a JSON array is read as several keywords. Before, its daily "new listings only" monitor billed every listing every day; now its second run billed only 10 listings it had not delivered and skipped the 9 it had (runs jOUBlB7uS0iSxxwIJ, 7z0PGYlosQsXxtSz1).
A price-band walk (above 2,040 per search) under a spending limit worth fewer rows now walks bands until the limit (1.9 read one page and delivered 60).
Price-band walks (above 2,040 per search) deliver and bill page by page: the run timeout, the spending limit or a refused page keeps every listing already read (before, an interrupted walk lost them all). excludeDatasetIds: listings already in the datasets of earlier runs are skipped, free, so a big job carries on without paying twice; a walk stopped by its timeout prints the value to paste. A run the platform restarts (moved, rebooted, resurrected) reads its own dataset back and never delivers or bills a listing twice.
An empty first page of a seller or store, or of a monitor that has delivered before, is read once more on another IP before it counts as "nothing found" (one seller with 96 listings came back empty once in 21 seller searches, run cptr3Uw0dzibxXBtw).
Every run says what it left out and why: left_out by reason and a note on each status row, left_out in SUMMARY, and the run card ("40 left out free: 38 without every search word in the title, 2 from eBay's results matching fewer words"; "1 found nothing").
Inputs without the new fields get the same listings and charges as 1.9, apart from the fixes above; the status row has two new keys (left_out, note).
1.9 — 2026-11-18 — More than eBay's 2,000 per search; sold auctions for monitors (add-on, not active yet)
Past eBay's ~2,000 listings per search: maxResultsPerQuery above 2,040 (now up to 100,000), or maxItems above 2,040 with one keyword, cuts the search into price bands eBay shows in full. A band whose first page reports more than 1,900 listings is cut in two and that page is only a probe (nothing delivered or charged from it). Bands run cheapest first (dearest first for price_high), position counts across the whole search, results_total is the whole search's count, and SUMMARY reports price_bands. Other scrapers' splitByPrice: true asks for every band, and their counts above 2,040 walk bands too. An explicit pages of 2-33 and onlyNew monitors keep reading only their pages.
includeSoldAuctions (with onlyNew, which it turns on): an auction a monitored search delivered is read again on its own page once it has ended (eBay shows an ended listing's result signed out: 10 of 10 read on 2026-11-18, catalogue listings with nordt=true). Sold ones are delivered as change = sold rows with the final price, bids, ended_at and previous_price (when in the same currency); unsold ones are counted in SUMMARY. Each auction is read once, at most 100 a run. A new event, sold_item, priced per sold auction: not active until its price is set (owner decision), so until then the run reads nothing for it, charges nothing and lists addons_inactive: ["sold"].
Monitor memories now keep an auction's end time with its price; older memories still read.
Inputs without the new fields get the same listings and charges as 1.8; maxResultsPerQuery up to 2,040 changes nothing.
Sessions that passed eBay's bot wall are kept for your next runs (reuseSessions, on by default): the next run reopens them on the same IP with their cookies and needs no real-browser page. The IP is checked before any cookie is replayed; stale cookies get one browser page on the same IP; a session whose browser had not finished loading by the end of the run (it waits up to 25 s) is kept without cookies, so the next run opens its browser on that proven IP; two runs at once never share a session. Stored in the key-value store ebay-search-sessions of your account (24 h for datacentre sessions, 20 min for residential). Measured 2026-11-18: first row 30.5 s on a cold run, then 5.8 s and 6.0 s with no browser.
excludeWords: words or phrases to leave out of titles. Single words reach eBay as -word; phrases, and whatever eBay lets through, are dropped before billing (filtered, and excluded in SUMMARY). Other scrapers' excludeKeywords (a list or one string) and negativeKeywords are read as ours; days with excludeKeywords is still read as epicscrapers' sold request and refused free.
New free columns. Every row: coupon and coupon_price ("From £213.39 with coupon"). Item-page rows (item URLs, and the details add-on from 2026-12-02): returns_accepted, return_days, return_shipping_paid_by, coupon_code, seller_type, parts compatibility (compatibility_count and the first 20 vehicles), and for private sellers on ebay.co.uk, .fr and .it the Buyer Protection fee split out of the price (buyer_protection_fee, price_before_fee; checked on a live UK listing: £120.30 = £115.00 + £5.30).
Fix: an item URL whose listing has ended is now a free no_results row with the end time. Before, an ended listing's page was delivered and billed as an active listing. Item pages are read with nordt=true, so an ended catalogue listing is no longer answered with its product page.
Inputs without the new fields get the same listings, filters and charges as 1.7.
1.7 — 2026-11-17 — Item-details add-on
includeDetails (off by default): each delivered search listing is enriched with its item page: description text, image gallery, variations (attributes, price, stock), brand, model, MPN, GTIN/UPC/EAN/ISBN, eBay product id, item specifics, quantity sold, category id, and the seller's username, feedback score, items sold, member-since date and Store URL. New event item_details: $0.0025 per enriched listing ($0.0022 on Scale, $0.002 on Business), charged only for rows whose page was read, never above maxTotalChargeUsd. Active from 2026-12-02; until then a run with includeDetails returns plain rows, charges nothing for details and lists addons_inactive in SUMMARY. memo23's and khadinakbar's detailedItems is read as ours.
Item URLs now carry the same detail columns (description included) at the listing price, and their seller_feedback_count is filled from the seller card.
A request now waits up to 30 s for a busy session before opening another browser (was 8 s): a browser costs 10-40 s and 1-2 MB, and five item pages read on one session take about ten.
onlyNew's memory now keeps each listing's currency: a price seen in another currency is not reported as a price change (1.6 memories still read). For multi-variation listings price is the lowest variation price eBay shows, so a change in that bound counts as a price change.
Without includeDetails and item URLs nothing changes: same rows and columns.
Five more marketplaces: co.uk, ca, ie, at and ch. They answered only eBay's JavaScript challenge to plain HTTP since August; the run's real browser clears it (re-measured 2026-11-17 on each host, item and search pages on the same IP after it).
sellers: eBay usernames or Store/profile URLs. Alone, each seller's active listings; with queries, keywords searched within those sellers only. /str/, /usr/ and /sch/<name>/m.html links work in startUrls too; a Store link is read once (free) for its seller's username. Other scrapers' seller/sellers fields are read as ours.
onlyNew (and includePriceChanges): for scheduled runs, deliver and bill only listings this search has not delivered before (and, optionally, those whose price changed, with change and previous_price). The memory is the key-value store ebay-search-seen in the caller's account. memo23's monitoringMode/enablePriceMonitoring and khadinakbar's onlyNewItems are read as ours.
Residential exits are pinned to the marketplace's country (US for ebay.com, GB for ebay.co.uk …), also in a RESIDENTIAL proxyConfiguration without a country. eBay shows every visitor the listings that ship to them in their own currency: on 2026-11-17 the same ebay.com seller search answered a South Korean exit in KRW (12,000 results), a US exit in USD (19,000) and a third country with nothing.
Reliability: until a marketplace has let the run in once, a page gets up to 16 attempts instead of 8 (on 2026-11-17 eBay's wall let a browser through on 1 in 23 datacentre and 10 in 29 residential IPs, so 8 attempts ended about 1 run in 12 with nothing). Requests wait for a session whose browser is still settling instead of opening another browser.
Without the new fields nothing changes: same rows, columns, prices and defaults.
1.5 — 2026-11-17 — Other scrapers' inputs, sold requests refused for free, item URLs back
Inputs written for other eBay scrapers now run: their field names (keywords, searchQuery, searchQueries, ebaySite, marketplace, count, maxResults, maxPages, condition, conditionId, listingType, categoryId, sortOrder and more) are read as ours wherever our own field is not set, and their values too ("ebay.com", "www.ebay.de", "US", "buyItNow", "price_asc", "refurbished", eBay's numeric ids). SUMMARY lists them as aliased_fields. memo23- and epicscrapers-shaped inputs keep their per-search meaning of maxItems. See the README section "Inputs from other scrapers work too".
Unknown input fields are ignored instead of failing, and listed as ignored_fields in SUMMARY and at the end of the status message. Input problems write SUMMARY with status: invalid_input.
A sold or completed request (sold search URL, mode: "sold", daysToScrape, soldWithinDays, includeCompletedListings: true, the "ended recently" sort) now ends at once, free, with the reason. Before, a pasted sold URL lost its sold flag and active listings were delivered and billed in its place. Re-measured 2026-11-17 with a real browser: eBay sends every sold search to its sign-in page.
Prices accept decimals (minPrice: 49.99), and rival spellings of buyingFormat, sortBy and conditions no longer make Apify reject the run before it starts. New buyingFormat: "best_offer" (listings that accept offers), conditions: ["refurbished"] (all five refurbished grades), category: "0" (all of eBay).
domain accepts "ebay.com", "www.ebay.de", country codes and eBay's EBAY_US-style ids.
Fix: on catalogue-matched cards (phones, clothing) the condition column held the product line ("Apple iPhone 13", "Size M") on about two thirds of the rows; it now reads the condition row. ebay.co.uk-style "from Australia" locations are read too.
Faster small runs: the first page comes back as soon as eBay has sent it; the browser finishes loading in the background, and only the session's next page waits for its cookies. A one-page run no longer waits for the browser to settle (a passing browser page took 7-27 s instead of 37-43 s in the release runs). Requests that arrive while a browser is opening wait for its session instead of queueing more browsers, so three item URLs cost one browser, not three.
Fixes: an item URL whose page showed a promoted listing first was refused as "the page is for another item" (the page's canonical link now decides); a 404 from eBay is reported at once as not found instead of being retried on eight IPs; a run that ended on a refused page no longer leaves its browser running (it kept the container alive until the run timeout).
Item URLs are a supported mode again (they answered on every session that passed eBay's wall on 2026-11-17); the README's and the event text's "item pages unreliable" notices are gone.
No prices changed; the event text was corrected with a text-only pricing record. Output fields and defaults are unchanged.
1.4 — 2026-11-16
maxItems is now shared fairly: every keyword and URL first gets an equal share (maxItems / targets), then rows left unused go to targets that still have listings, so 5 keywords with maxItems 20 return 4 listings each instead of 20 from the first; a target the cap never reaches is still never fetched (no browser session opened for it). Rows read but not yet delivered wait for the next turn instead of being read again, and a later page that fails no longer loses the rows already read. Near the run timeout the run starts no new target or page and ends green with SUMMARY written instead of being killed. Without maxItems, results are unchanged. No prices, output fields, defaults or input fields changed.
1.3 — 2026-11-16
maxItems (sent by AI agents) now caps the primary rows delivered and charged; add-ons follow the delivered rows. It is one total of listing rows across all keywords and URLs, and each page asks for its rows before it is fetched, so a run stops fetching, and opening browser sessions, the moment the cap is reached; targets it never reached get a free limit status row. With pages left at its default, maxItems also lifts the page limit (up to 34 pages per search) so the run can deliver up to maxItems listings; an explicit pages or maxResultsPerQuery is the stricter cap and wins. Without maxItems nothing changes. No prices, output fields, defaults or input fields changed.
1.2 — 2026-11-16 — Searches work again behind eBay's new bot wall
Since 2026-11-13, eBay's Akamai Bot Manager has refused every plain HTTP request with a 403 "Error Page". This happened on every proxy pool and every TLS fingerprint, so every run failed. Nothing was charged.
Each proxy session now opens with one page request from a Camoufox (Firefox) browser, through that session's own IP. The session then fetches its later pages with that browser's cookies and User-Agent. When eBay refuses a page, the session closes and the next one opens on a fresh IP.
The actor now runs on Apify's Camoufox Python image and needs 2 GB of memory, which is the new default and minimum. With 512 MB the browser crashed, and with 1 GB it timed out. Compute stays included in the per-listing price.
Inputs, output fields, prices, free status rows and charged == delivered are unchanged.
2026-11-13 — Restore previous listing keywords
Restore title, description and SEO text to the November 5 baseline at the owner’s request. Preserve current runtime fixes, input/output contracts, billing, prices and defaults.
2026-11-06 — MCP discovery metadata
Clarify supported search intents and output nouns in the Store listing. Runtime, input contract, output and prices are unchanged.
Changelog
2026-11-12 — Retry and billing safeguards
Clamp each charge batch to the remaining event budget before calling the SDK, including when concurrent fetches finish after another job spends part of the cap.
A transient residential proxy error now rotates the session without disabling the fallback pool. Only an explicit proxy authentication failure disables that pool.
Check the remaining event budget before each target and limit pagination to affordable rows. Runs with no affordable rows make no source requests.
Stop on billing-service failures without delivering unpaid listings or reporting unconfirmed charges. SUMMARY.billing_error records the failure; prices and listing fields are unchanged.
2026-11-06 — Item-detail availability notice
Narrow the listing to active search rows and prominently disclose that item-page details are currently unreliable. The same-build US check returned 3 search listings, but all 3 fresh item URLs were blocked by eBay challenge/error pages, with no detail rows or item charges. This small current check does not establish permanent failure for every item page.
Qualify item-specifics claims in the description, pricing event, input form and README. Search success does not guarantee detail delivery; the two-run contract is documented without presenting it as a verified enrichment workflow.
Replace a contradictory UK search example with a supported US URL. Keep the current $0.004-per-delivered-row pricing examples and unsupported-marketplace limits.
No runtime behavior, output fields, accepted inputs, types, defaults, enums, prefills or prices changed.
2026-11-06 — Agent metadata clarity
Correct current price examples to $0.004 per listing, $0.24 per 60-row page, and $2.40 for 600 delivered rows.
Explain the two-run search-to-item-details workflow and its separate per-run charges; item specifics are not fetched automatically by keyword searches.
State UK and sold/completed modes are unsupported, and qualify pasted-URL filter preservation. Correct the supported marketplace count to 10.
No runtime behavior, output fields, input names/types/defaults/enums/prefills, or prices changed.
2026-10-16 — Keyword Planner and locale documentation
Validated search terminology against Google Ads Keyword Planner and Store shelves. Added localized usage guidance and bounded examples; retained existing English phrases. Clarified locale limitations where measured. Corrected current-versus-scheduled price wording and arithmetic. No runtime, output fields, defaults, or pricing changed.
price change, set 2026-10-12, effective 2026-10-27
item $0.003 → $0.004 per row (rivals charge $0.003–0.005 per item plus $0.02 to start). the actor has paying users, so Apify applies the increase on 2026-10-27 and notified them; until then the old price bills and the listing text below describes the price from that date; nothing else changes — same rows, same free rows, same filters, no start fee, proxy and compute included. Every price mention in the input form, the event text and this README was updated with it.
1.1 — warm-up follows the URL's marketplace; ebay.at withdrawn, 2026-10-11
No output or price changed; the same inputs return the same rows, except that domain: "at" is now refused before anything is charged.
ebay.at withdrawn from the offered marketplaces: it answers eBay's anti-bot challenge on every proxy pool and from a home IP (0 of 47 attempts on 2026-10-11), the posture eBay UK/Ireland/Canada/Switzerland/Hong Kong have had since August. The card and the domain input now say 10 marketplaces.
Reliability: a pasted startUrls link on a marketplace other than the run's domain (the default is com) failed every try with eBay's Akamai 403 ("Error Page | eBay", reference-id). The client warms each proxy session with a GET of the marketplace homepage to collect the bm_s/bm_so cookies the next request is scored against, and it warmed on the run's domain — but those cookies are scoped Domain=.ebay.<tld>, so a session warmed on ebay.com reached ebay.de with no cookie at all and was scored as cold. Measured 2026-10-11 on residential proxies, ebay.de search page: 0 of 9 after an ebay.com warm-up, 0 of 8 cold, 8 of 10 after an ebay.de warm-up; two cloud runs of the ladder's ebay.de URL case failed 8 of 8 tries each. The warm-up now follows the host of each request, once per session and host, so one run can mix marketplaces in startUrls as the input form promises. Keyword runs on a single domain are unaffected (they always warmed on the right host).
Test: today's ebay.de 403 body is a fixture (it is Akamai's error page, not a consent or captcha page) and an offline test pins the warm-up order: ebay.de/ before the first ebay.de request, ebay.com/ before the first ebay.com one, never twice per host.
1.0 — listing and input form reworded, 2026-10-11
No behaviour, output or price changed; the same inputs return the same rows.
Title tail adds "Items" next to the head phrases agents type ("Search, Listings", "Prices", "Sellers"). Description names one row per listing and its fields, the item-page extras (item specifics) and every filter eBay applies before billing; "search results" and "price tracker" move to seoDescription, which the Store search indexes.
seoTitle names the API; seoDescription carries the secondary phrases (ebay prices, ebay search results, items, auctions, Buy It Now, seller feedback, product data, price tracker) and the German nouns (Angebote, Preise).
Pricing event text states the per-1,000 price in words, the 60-listings-per-page fact, what is never charged, that there is no start fee and that the run stops at the maximum cost per run set when starting it. Price unchanged.
Input form reordered: pages and maxResultsPerQuery (the bill) right after the marketplace, then the eBay-side filters, then sessions, perIp and proxy. Every field description carries a literal example, says what 0/empty means and names the user request it answers. Property names, types, defaults, enums and prefills are byte-identical.
README: new section "eBay scraper for AI agents: which input answers which request?" (when to use / when not, request → input table, row fields and the status/empty contract); the intro now says 11 marketplaces, which is what the actor offers.
2026-08-30
Reliability: a run that cannot act on its input — a URL from the wrong site, a name nothing resolves to, an empty target list, a number outside the documented range — now ends cleanly with the reason on the run card instead of as a failed run. Nothing is charged in either case; a blocked or throttled source still fails loudly.
Store listing: moved into the categories buyers actually browse (the old Business category has no Store page).
1.0 — 2026-08-29
First release.
eBay active listings from search results pages and item pages, on 11 verified marketplaces (com, de, fr, it, es, at, nl, pl, com.au, com.sg, com.my). eBay UK, Ireland, Canada, Switzerland and Hong Kong answer an anti-bot challenge on every proxy pool we can reach (18/18 attempts on 2026-08-29) and are not offered; their URLs are still labelled and priced correctly if pasted into startUrls.
Demand signals on every search row: units_sold, watchers, bids, time_left, best_offer, list_price and discount_pct.
minPrice / maxPrice are sent to eBay as _udlo / _udhi so they filter server-side, then re-checked before billing; filtered rows are never charged.
60 listings per page (_ipg=60); the two aria-hidden "Shop on eBay" placeholder cards eBay renders on every results page are dropped rather than delivered.
A zero-result search delivers nothing: eBay's null-search page still renders about twenty "results matching fewer words" cards belonging to other searches.
All four eBay refusals — the Akamai 403 error page, the /splashui/challenge interstitial, the sign-in gate and the "Security Measure" page — are reported as status='error', never as "no results".
Every item id is delivered and billed once per run; charged == delivered in every input mode and at every spending limit.
Six dataset views: Overview, Demand signals, Sellers, Price research, Item pages, Run status.
Completed/sold search is not included: eBay redirects logged-out callers to its sign-in gate on every marketplace and route (verified 2026-08-29). See the FAQ.