/aliexpress/products/reviews

POST /api/aliexpress/products/reviews

Price: 1 credit

Get buyer reviews for an AliExpress product by id or product URL. Each review carries the review text, star rating, buyer name/country/gender/avatar, review date, purchased SKU, shipping method, photos, helpful votes, follow-up review text and photos, and the structured review labels (aspect and value). Supports filtering by subset (all, photo reviews, follow-up reviews, local reviews) and translation into the requested language.

How to use it

Fetch buyer reviews of an AliExpress product. Each item has id, text, rating (1-5), buyer_name, buyer_country, buyer_gender, buyer_image, created_at (unix seconds) and created_at_text, sku_id and sku_text, logistics, images, up_vote_count/down_vote_count, is_anonymous, additional_text/additional_images for follow-up reviews and labels with the buyer's per-aspect answers. A product with no reviews yet answers with an empty list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• language string — Content language. On endpoints without a separate country field it also selects the shopping region, which drives availability, shipping options and delivery estimates (default: "en_US"; one of: "ar_MA", "de_DE", "en_US", "es_ES", "fr_FR", "in_ID", "it_IT", "iw_IL", "ja_JP", "ko_KR", "nl_NL", "pl_PL", "pt_BR", "ru_RU", "th_TH", "tr_TR", "vi_VN")
• currency string — Currency the prices are returned in (default: "USD"; one of: "USD", "EUR", "GBP", "CAD", "AUD", "RUB", "BRL", "CLP", "JPY", "KRW", "CHF", "SEK", "PLN", "ILS", "NOK", "DKK", "NZD", "MXN", "COP", "TRY", "THB", "SGD", "MYR", "PHP", "IDR", "INR", "VND", "HKD", "TWD", "AED", "SAR", "CZK", "HUF", "RON", "BGN", "UAH", "KZT", "ARS", "EGP", "ZAR", "CNY", "PEN")
• product string required — Product id or product page URL (examples: "3256810343908999", "https://www.aliexpress.com/item/1005010530223751.html"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)
• filter string — Review subset to return (default: "all"; one of: "all", "image", "additional", "local")
• translate boolean — Return the translated review text when the buyer wrote in another language (default: true)

Response

• @type string (default: "AliexpressProductReview")
• id string required
• text string nullable
• rating number nullable
• buyer_name string nullable
• buyer_country string nullable
• buyer_gender string nullable
• buyer_image string nullable
• created_at integer nullable
• created_at_text string nullable
• sku_id string nullable
• sku_text string nullable
• logistics string nullable
• images array (default: [])
• up_vote_count integer nullable
• down_vote_count integer nullable
• is_anonymous boolean (default: false)
• additional_text string nullable
• additional_at_text string nullable
• additional_images array (default: [])
• labels array (default: [])
  • @type string (default: "AliexpressProductReviewLabel")
  • name string required
  • value 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 — The entity was not found, or a precondition failed 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.