eBay Product Scraper API

An eBay product scraper is a tool that reads a single eBay item page and returns its data in a structured format. Our eBay product scraper API takes an item URL (or the numeric id) and returns title, price, currency, url, image, brand, description, availability, old_price, identifiers, item specifics, item_id, and condition as JSON from one request.

Send one GET request to our ebay/product endpoint with the item url and your API key. We fetch the page over residential proxies, handle eBay's anti-bot checks, retry on failure, and parse the listing's JSON-LD into clean JSON, so you do not maintain selectors against eBay's item-page DOM, which changes often.

Either works. Pass the full item URL to the url parameter, or pass the numeric item id to the id parameter and we build the canonical /itm/{id} URL for you. One of the two is required. Passing the URL from an eBay search result straight into this endpoint is the common pattern for going from a result card to full item detail.

Yes, price and currency come from the listing's JSON-LD offer, and a discounted item also returns old_price from the offer's price specification. One thing to know: eBay localises the offer price to the egress IP's country, so the same listing can render a different currency and amount from different regions. Use the country parameter to pin the region you want.

ids is an array of product identifiers found in the listing's structured data, each an object such as { mpn: ENV155BAE } or { gtin13: ... }, which lets you match an eBay item to your own catalog. additional_properties is an array of item specifics as { name, value } pairs when the seller published them; it comes back empty for listings that expose none, as in the sample above.

We read condition from the item page's condition block. On most listings that yields a value like Brand New or Pre-Owned, but some pages render only the field label (Condition) and load the value in a later state, in which case the field returns the label as-is rather than a fabricated value. When you need condition reliably across a set of items, the search endpoint also reports each card's condition in its results.

Median end-to-end response is about 2.6 seconds, including residential proxy routing, anti-bot handling, retries, and parsing. One call returns the full item payload, so you do not chain requests to assemble a single listing.