/peerspot/products/reviews

POST /api/peerspot/products/reviews

Price: 20 credits

List PeerSpot reviews of an enterprise software product in the order PeerSpot pages them: title, star rating, date, reviewer role, company size and industry, and the full answers to each review question (use case, valuable features, room for improvement, pricing, ROI, support, setup).

How to use it

Read what practitioners report about a product. sections carries the answer to each review question keyed by topic, so filter on key for setup_cost or room_for_improvement.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — PeerSpot product URL or its slug (examples: "https://www.peerspot.com/products/splunk-enterprise-security-reviews", "splunk-enterprise-security"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1; max: 300)

Response

• @type string (default: "PeerspotProductReview")
• id string required
• url string nullable
• product_alias string required
• review_title string nullable
• rating integer nullable
• created_at integer nullable
• author_name string nullable
• author_alias string nullable
• author_title string nullable
• author_labels array (default: [])
• company_size string nullable
• industry string nullable
• job_level string nullable
• word_count integer nullable
• sections array (default: [])
  • @type string (default: "PeerspotReviewSection")
  • key string required
  • question string nullable
  • text string required

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 PeerSpot product at this slug 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.