/pcpartpicker/builds/comments

POST /api/pcpartpicker/builds/comments

Price: 5 credits

Return the comment thread under one completed PCPartPicker build: each comment with its author, the author's profile link and avatar, how long ago it was posted, its text, its permalink, and its position in the reply tree.

How to use it

The thread arrives flattened in display order: `depth` 0 is a top-level comment and `parent_id` points at the comment being replied to, so rebuilding the tree needs no second call. `posted_ago` is the relative wording the site shows ('9 months ago'), not a date. A build with no discussion returns an empty list under a 200. Deleted comments keep their place in the thread with no author and no text.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• build string required — PCPartPicker completed-build code, or any pcpartpicker.com /b/ URL (examples: "m6mrxr", "https://pcpartpicker.com/b/m6mrxr"; minLength: 1)
• region string — PCPartPicker country site to read the build from (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 comments to return (min: 1)

Response

• @type string (default: "PcpartpickerComment")
• id string required
• author string nullable
• author_url string nullable
• author_avatar string nullable
• posted_ago string nullable
• text string nullable
• permalink string nullable
• depth integer (default: 0)
• parent_id 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 build 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.