/getapp/products/reviews

POST /api/getapp/products/reviews

Price: 20 credits

Get GetApp (getapp.com) product reviews by alias, category/alias path, or product URL

How to use it

Get user reviews of a GetApp (getapp.com) software product by alias, path, or URL. GetApp publishes pros and cons excerpts rather than a review body, so 'text' stays empty. Only a subset of a product's reviews is published, so a count larger than that subset returns everything available.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — GetApp product identifier. Accepts product alias ('zoho-crm'), '{category}/a/{alias}' path, or full product URL. (examples: "zoho-crm", "https://www.getapp.com/customer-management-software/a/zoho-crm/"; minLength: 1; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.|getapp\.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: "GetappReview")
• id string required
• headline string nullable
• text string nullable
• pros string nullable
• cons string nullable
• topics array (default: [])
• advice string nullable
• rating number nullable
• ratings object nullable
  • @type string (default: "GetappReviewRatings")
  • value_for_money number nullable
  • functionality number nullable
  • ease_of_use number nullable
  • customer_support number nullable
  • recommendation number nullable
• written_at integer nullable
• source_site string nullable
• vendor_response string nullable
• author object nullable
  • @type string (default: "GetappReviewAuthor")
  • name string nullable
  • job_title string nullable
  • company_size string nullable
  • industry string nullable
  • image string nullable
  • is_verified boolean 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 — 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.