POST /api/ebay/items/search
Price: 10 credits
Search active eBay listings by keyword: for each result returns title, price/currency, condition, image, buying format, shipping, sold and watcher counts and a brief seller summary. Supports filters by condition, buying format, price range and category.
Search live eBay listings for a keyword. Returns items with price/currency, list_price (if discounted), condition, image, buying_format (auction/buy_it_now), bid_count (auctions), has_best_offer, shipping, sold_count, watcher_count and seller (name/positive_percent/feedback_count). Filter by condition, buying_format, min_price/max_price, category_id and sort.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)keyword string required — Search keyword (examples: "nintendo switch oled"; minLength: 1)count integer required — Max number of listings to return (min: 1; max: 10000)sort string — Result ordering (default: "best_match"; one of: "best_match", "ending_soonest", "newly_listed", "price_low", "price_high")condition string nullable — Filter by item condition (one of: "new", "open_box", "used", "parts")buying_format string nullable — Filter by buying format (one of: "auction", "buy_it_now")min_price number nullable — Minimum price (min: 0)max_price number nullable — Maximum price (min: 0)category_id string nullable — eBay category ID to scope the search@type string (default: "EbaySearchItem")id string requiredurl string requiredprice number nullablecurrency string nullablelist_price number nullablecondition string nullableimage string nullablebuying_format string nullablebid_count integer nullablehas_best_offer boolean (default: false)shipping string nullablesold_count integer nullablewatcher_count integer nullableseller object nullable@type string (default: "EbaySearchSeller")name string nullablepositive_percent number nullablefeedback_count integer nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.