/pcpartpicker/products/suggestions

POST /api/pcpartpicker/products/suggestions

Price: 5 credits

Look a product up by name across every PCPartPicker component category at once and get back its product code, canonical name, category and image.

How to use it

Use this to turn a product name a user typed into a code and a category, then pass the code to /pcpartpicker/products or the category to /pcpartpicker/products/search. It is the only cross-category lookup here and it is a typeahead: it answers with a short best-match list rather than everything that matches, and it carries no price or specs. A query that matches nothing returns an empty list rather than an error, and emptiness means the wording matched no part name.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Keyword matched against product names across every component category (examples: "rtx 5070", "9800x3d", "kingston nv3"; minLength: 1)
• region string — PCPartPicker country site to query (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")
• count integer required — Max number of results to return (min: 1; max: 10)

Response

• @type string (default: "PcpartpickerProductSuggestion")
• id string required
• url string nullable
• name string nullable
• category string nullable
• image 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 — 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.

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.