/softwareadvice/products/reviews

POST /api/softwareadvice/products/reviews

Price: 20 credits

Get Software Advice (softwareadvice.com) product reviews by category-scoped profile path or URL

How to use it

Get user reviews of a Software Advice (softwareadvice.com) software product by its category-scoped profile path or URL. Returns each review's headline, text, pros, cons, overall and secondary ratings, usage frequency, incentive, vendor response, author profile, and prior edited versions.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Software Advice product identifier. Accepts the category-scoped profile path ('crm/zoho-crm-profile' or '/crm/zoho-crm-profile/') or the full profile URL. (examples: "crm/zoho-crm-profile", "https://www.softwareadvice.com/crm/zoho-crm-profile/"; minLength: 1; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.|softwareadvice\.com)[^\s]*|/?[A-Za-z0-9][A-Za-z0-9._/\-]*)$)
• count integer required — Max number of reviews to return (min: 1)

Response

• @type string (default: "SoftwareadviceReview")
• id string required
• headline string nullable
• text string nullable
• pros string nullable
• cons string nullable
• rating number nullable
• ease_of_use_rating number nullable
• customer_support_rating number nullable
• functionality_rating number nullable
• value_for_money_rating number nullable
• frequency_of_using string nullable
• used_for string nullable
• reason_for_choosing string nullable
• reason_for_switching string nullable
• incentive string nullable
• is_anonymous boolean nullable
• written_at integer nullable
• vendor_response string nullable
• author object nullable
  • @type string (default: "SoftwareadviceReviewAuthor")
  • name string nullable
  • company_size string nullable
  • industry string nullable
  • is_validated boolean nullable
  • image string nullable
• previous_versions 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 — Product not found 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.