/dhgate/stores/reviews

POST /api/dhgate/stores/reviews

Price: 5 credits

Get the buyer reviews received by a DHgate store (seller), by store id, store URL or seller id. Each review carries the buyer name and country, the star rating, the review text, the date, helpful and unhelpful vote counts and the reviewed product (id, title, image, url). Supports filtering by review type (all, positive, neutral, negative) and by date window.

How to use it

Fetch reviews received by a DHgate seller. Each item has buyer_name, buyer_country, buyer_country_code, rating (1-5), text, created_at (unix seconds) and created_at_text, helpful_count, unhelpful_count and the reviewed product (id, product_title, image, product_url). A seller with no reviews answers an empty list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• store string required — Store id, store URL, or seller id (examples: "22224092", "8aaa057596ae7fef0196aebc841f02f7"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)
• type string — Review subset to return (default: "all"; one of: "all", "positive", "neutral", "negative")
• date_range string — Only reviews within this window (default: "all"; one of: "last_30_days", "last_60_days", "last_90_days", "last_180_days", "last_year", "all")

Response

• @type string (default: "DhgateStoreReview")
• buyer_name string nullable
• buyer_country string nullable
• buyer_country_code string nullable
• rating number nullable
• text string nullable
• created_at integer nullable
• created_at_text string nullable
• helpful_count integer nullable
• unhelpful_count integer nullable
• product object nullable
  • @type string (default: "DhgateReviewProduct")
  • id string nullable
  • product_title string nullable
  • image string nullable
  • product_url string 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 — Store not found on DHgate 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.