/influenster/products/reviews

POST /api/influenster/products/reviews

Price: 1 credit

Get Influenster (influenster.com) reviews for a product by slug or numeric id

How to use it

Get customer reviews for a product on Influenster (influenster.com) by its slug or numeric id. Returns each review's title, text, star rating, like count, incentivized flag, created and updated timestamps, the reviewer profile, and attached photos. Sort by new, trending, or top.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Product slug, numeric product id, or full product review-page URL (examples: "maybelline-new-york-great-lash-mascara", "1382772"; minLength: 1; pattern: ^(?:https?://\S+|[^/\s][^\s]*)$)
• count integer required — Number of reviews to return (min: 1)
• sort string — Review sort order (default: "new"; one of: "new", "trending", "top")

Response

• @type string (default: "InfluensterReview")
• id integer required
• review_title string nullable
• text string nullable
• stars integer nullable
• like_count integer nullable
• is_incentivized boolean (default: false)
• created_at string nullable
• updated_at string nullable
• user object nullable
  • @type string (default: "InfluensterReviewUser")
  • id integer required
  • short_name string nullable
  • image string nullable
  • is_pro boolean (default: false)
• 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 — 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.