/pcpartpicker/products

POST /api/pcpartpicker/products

Price: 5 credits

Fetch one PCPartPicker component by its product code and return the full spec sheet together with the live merchant price table — every seller with its base price, promo, shipping, tax, stock state, the total and the outbound buy link — plus the manufacturer, part numbers, product images and the community star rating with its number of ratings.

How to use it

Takes the six-character code from a /product/ URL; the slug after it is optional and a full URL is accepted as given. `region` decides which merchants and which currency appear in `offers`, so a product with sellers in the US may come back with an empty `offers` list on another country site while the specs stay the same. `lowest_price` is derived from the merchant table on this page, which is why it can differ from the `price` field that /pcpartpicker/products/search reports for the same product. Codes are shared across the whole site, so a code taken from a build, a part list or a guide resolves here unchanged. This endpoint's `specs` entry is {name, values: list[str]} — a spec can carry several values here; /pcpartpicker/products/search carries its own, differently-shaped `specs` ({name, value: str}).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — PCPartPicker product code, or any pcpartpicker.com product URL (examples: "h7RnTW", "https://pcpartpicker.com/product/h7RnTW/"; minLength: 1)
• region string — PCPartPicker country site, which decides the merchants and the currency of every price (default: "us"; one of: "au", "at", "be", "ca", "cz", "dk", "fi", "fr", "de", "hu", "ie", "it", "nl", "nz", "no", "pl", "pt", "ro", "sa", "sk", "es", "se", "uk", "us")

Response

• @type string (default: "PcpartpickerProduct")
• id string required
• url string required
• name string nullable
• category string nullable
• category_slug string nullable
• manufacturer string nullable
• part_numbers array (default: [])
• description string nullable
• image string nullable
• images array (default: [])
• rating number nullable
• review_count integer nullable
• lowest_price number nullable
• specs array (default: [])
  • @type string (default: "PcpartpickerProductSpec")
  • name string required
  • values array (default: [])
• offers array (default: [])
  • @type string (default: "PcpartpickerOffer")
  • merchant string required
  • merchant_name string nullable
  • url string nullable
  • base_price number nullable
  • promo string nullable
  • shipping string nullable
  • tax string nullable
  • availability string nullable
  • total_price number nullable
  • note 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 — No product with that code, or the page came back without a product breadcrumb 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.