/ebay/products

POST /api/ebay/products

Price: 10 credits

Get eBay catalog product details by ePID (or catalog URL): title, brand/model/mpn/upc, images, aggregate rating, price range across listings, listing count, product specs and category.

How to use it

Fetch a single eBay catalog product by ePID (eBay Product ID) or a catalog product URL. Returns one product with title, brand/model/mpn/upc/gtin13, image+images, rating and review_count, lowest_price/highest_price/currency across active listings, listing_count, specs (key/value), breadcrumbs+category and description.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — eBay product ID (ePID) or a catalog product URL containing it (examples: "4062765295", "https://www.ebay.com/p/4062765295"; minLength: 1)

Response

• @type string (default: "EbayProduct")
• id string required
• url string required
• brand string nullable
• model string nullable
• mpn string nullable
• upc string nullable
• gtin13 string nullable
• image string nullable
• images array (default: [])
• rating number nullable
• review_count integer nullable
• lowest_price number nullable
• highest_price number nullable
• currency string nullable
• listing_count integer nullable
• specs object (default: {})
  • * string
• breadcrumbs array (default: [])
• category string nullable
• description string nullable

Errors

• 422 — 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 — Product not found (well-formed but nonexistent ePID) 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.