/pcpartpicker/products/history

POST /api/pcpartpicker/products/history

Price: 5 credits

Return the recorded price history of one PCPartPicker component as one dated series per merchant, with the lowest, highest and latest price each merchant charged over the chosen window.

How to use it

One result per merchant, not one per product, so a part sold by five shops comes back as five series and a part nobody has ever stocked comes back empty under a 200. Points are irregular — PCPartPicker records a point when a price moves, not on a fixed schedule — and a point with a null `price` marks the merchant dropping the part rather than a price of zero, so filter those out before averaging. `latest_price` is the last non-null point in the window, not necessarily the current price — if a merchant dropped the part after that point, `points[-1].price` is null while `latest_price` still shows what they last charged; check the last `points` entry to tell the two apart. `timestamp` is milliseconds since the epoch. PCPartPicker does not record Amazon in these graphs, so an Amazon offer visible on /pcpartpicker/products has no series here. `region` selects which country's merchants are tracked.

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")
• window string — Length of the recorded history to return, in days back from today (default: "120"; one of: "60", "120", "180", "365", "730")
• count integer required — Max number of merchant series to return (min: 1)

Response

• @type string (default: "PcpartpickerPriceHistory")
• series_id string required
• product_id string required
• merchant string required
• currency string nullable
• window_start integer nullable
• window_end integer nullable
• lowest_price number nullable
• highest_price number nullable
• latest_price number nullable
• points array (default: [])
  • @type string (default: "PcpartpickerPricePoint")
  • timestamp integer required
  • price number 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 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.