POST /api/newegg/products
Price: 5 credits
Get full Newegg product details by item number (or product URL): title, brand, model, price, list_price, rating, review_count, images, breadcrumbs, specifications, condition, availability, return policy and marketplace seller.
Fetch a single Newegg product by item number (e.g. N82E16814932611 or 9SIB...) or a product URL. Returns one item with title, brand, model, upc, price/list_price/price_min/price_max/currency, rating, review_count, condition, availability, in_stock, image+images, breadcrumbs+category, description, specifications (name/value map), warranty, return_policy_days, is_marketplace and seller (id/name/alias/rating/review_count).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)product string required — Newegg item number or a product URL containing it (examples: "N82E16814932611", "https://www.newegg.com/p/N82E16814932611"; minLength: 1)@type string (default: "NeweggProduct")id string requiredurl string requiredbrand string nullablemodel string nullableupc string nullableprice number nullablelist_price number nullableprice_min number nullableprice_max number nullablecurrency string nullablerating number nullablereview_count integer nullablecondition string nullableavailability string nullablein_stock boolean nullableimage string nullableimages array (default: [])breadcrumbs array (default: [])category string nullabledescription string nullablespecifications object (default: {})* stringwarranty string nullablereturn_policy_days integer nullableis_marketplace boolean nullableseller object nullable@type string (default: "NeweggSeller")id string nullablename string nullablealias string nullablerating number nullablereview_count integer nullableis_top_rated boolean 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 — Product not found (well-formed but nonexistent item number, or page has no product) 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.