/softwaresuggest/products/reviews

POST /api/softwaresuggest/products/reviews

Price: 10 credits

List the reviews SoftwareSuggest shows for a software product: title, text, star rating, date, reviewer name and role, company size, usage, what they like and dislike, and per-aspect scores.

How to use it

Read user reviews of one product. SoftwareSuggest serves at most 20 reviews per product page, while softwaresuggest/products states the product's full review count.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — SoftwareSuggest product URL or its alias (examples: "https://www.softwaresuggest.com/bamboohr", "bamboohr"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1; max: 20)

Response

• @type string (default: "SoftwaresuggestProductReview")
• id string required
• review_title string nullable
• text string nullable
• rating number nullable
• created_at integer nullable
• author_name string nullable
• author_title string nullable
• author_url string nullable
• author_image string nullable
• usage string nullable
• company_size string nullable
• labels array (default: [])
• pros string nullable
• cons string nullable
• scores array (default: [])
  • @type string (default: "SoftwaresuggestReviewScore")
  • name string required
  • score number required
• useful_count integer nullable
• product_alias 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 SoftwareSuggest product at this alias 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.