/pult/products/reviews

POST /api/pult/products/reviews

Price: 5 credits

List the customer reviews of one pult.ru product: the review body with its separate pros and cons, the star rating the author gave, the posting time, the photos attached to the review, and the author's display name, avatar and reviewer level on the site.

How to use it

Takes the numeric product id, not a slug or an article number — read it from the id field of any product result. Most products carry no reviews at all, and an id that does not exist answers the same empty list, so emptiness is not evidence the id is wrong. pros and cons are separate short fields the review form asks for, while text is the free-form body, and any of the three can be empty.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Numeric pult.ru product id, as returned in the id field of any product result (examples: "1481614"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)

Response

• @type string (default: "PultReview")
• id string required
• product_id string required
• text string nullable
• pros string nullable
• cons string nullable
• rating integer nullable
• created_at integer nullable
• topic_id string nullable
• author object nullable
  • @type string (default: "PultAuthor")
  • id string nullable
  • name string nullable
  • image string nullable
  • level integer nullable
  • level_label string nullable
  • review_count integer nullable
  • message_count integer nullable
  • thanks_count integer nullable
• images array (default: [])

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 — pult.ru rejected the product id. 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.