POST /api/upcitemdb/products
Price: 1 credit
Get a product by its barcode
Resolve one barcode to a product record with its retail offers. Pass the digits alone — EAN-8, UPC-A, EAN-13, GTIN-14 and ISBN-13 all resolve, and a GTIN-14 case code resolves to the consumer item it packs, so the barcode that comes back can differ from the one sent. The catalogue is US retail, so European and Japanese grocery barcodes are frequently absent and answer 412. Read `asin` when you need the Amazon listing for a barcode; it is a cross-reference the record carries, and no offer row ever points at Amazon.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)barcode string required — Barcode of the product: EAN-8, UPC-A, EAN-13, GTIN-14 or ISBN-13, digits only (examples: "0038000138416", "045496590475", "9780262033848"; minLength: 8; maxLength: 14)@type string (default: "UpcitemdbProduct")ean string (default: "")upc string (default: "")isbn string (default: "")asin string (default: "")elid string (default: "")product_title string (default: "")description string (default: "")brand string (default: "")model string (default: "")publisher string (default: "")category string (default: "")color string (default: "")size string (default: "")dimension string (default: "")weight string (default: "")currency string (default: "")lowest_recorded_price number nullablehighest_recorded_price number nullableimages array (default: [])offers array (default: [])@type string (default: "UpcitemdbOffer")merchant string (default: "")domain string (default: "")listing_title string (default: "")condition string (default: "")availability string (default: "")currency string (default: "")price number nullablelist_price number nullableshipping string (default: "")link string (default: "")updated_at integer (default: 0)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 — 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.