Scraping API · Lazada

Review text, ratings and the SKU each one belongs to.

Reviews are the only place a marketplace records what a buyer thought of a specific variant. This endpoint returns them by item ID, with the rating, the text, whether the reviewer bought the item, and which SKU they bought.

What one call returns.

  • The review total for the listing, so you know how deep the well is before paging
  • Rating, review text and the images attached to each review
  • isPurchased, separating verified buyers from the rest
  • skuId and skuFields, which tie a review to the variant it was written about

Use this when the question is about product experience rather than sales: which variant draws complaints, what wording repeats, how sentiment moves after a formulation change.

The specification.

Endpoint
POST /v1/lazada/product-reviews
Markets
Indonesia, and the other Lazada markets
Credits
Per request, see the rate card
Batch size
Up to 50 requests per call, five reviews each
Approval
None, runs on submission
Processing hours
Any hour

Checked against the live API specification on 2026-09-18.

A real response, not a mock-up.

POST /v1/lazada/product-reviews → GET /v1/lazada/retrieve/{task_id}Captured 2026-09-18
{
  "reviewTotal": 41568,
  "reviews": [
    {
      "reviewRateId": 2058651286080925,
      "itemId": 7990080925,
      "rating": 5,
      "isPurchased": true,
      "skuId": 14410196412,
      "skuFields": [],
      "likeCount": 1,
      "reviewContent": "Segar dan beraroma buah-buahan, Lembut di kulit, Lembut di kulit, Nilai uang yang baik, Kemasan pouch yang praktis, Cocok untuk penggunaan sehari-hari, Aroma tahan lama,  ",
      "images": [
        {
          "url": "https://lzd-u.slatic.net/1a67465340e243ccaff98365a58f12de_1b45767b28b341088cb4dafd173b46c6.jpg"
        }
      ]
    },
    {
      "reviewRateId": 2058543222380925,
      "itemId": 7990080925,
      "rating": 5,
      "isPurchased": true,
      "skuId": 14410196412,
      "skuFields": [],
      "likeCount": 1,
      "reviewContent": "📦Kemasan:Kemasan pouch yang praktis, \n 🌼Aroma: Aroma yang menyegarkan, \n Cocok untuk penggunaan sehari-hari, \nbarang sesuai pesanan suka sama Aroma nya busa melimpah. ",
      "images": [
        {
          "url": "https://lzd-u.slatic.net/bc29101c7bf24456a03c4a86f48229ec_922a3fc22fc8443c8d690b45cdd4754c.jpg"
        }
      ]
    },
    {
      "reviewRateId": 2056292333380925,
      "itemId": 7990080925,
      "rating": 5,
      "isPurchased": true,
      "skuId": 14410196412,
      "skuFields": [],
      "likeCount": 2,
      "reviewContent": "Nilai uang yang baik, Kemasan pouch yang praktis, wanginya enak dan kemasan ekonomis pengiriman cepat ",
      "images": [
        {
          "url": "https://lzd-u.slatic.net/a47570f5cd4b44a5bce7b5808bb121a1_04deefdfd8bb45f0812602d235c9a500.jpg"
        }
      ]
    }
  ]
}

The limits, stated plainly.

  • Five reviews per call. The listing we pulled while writing this page holds 41,568 reviews, which is 8,314 calls to read in full
  • Each page is a separate billed request, so agree a page budget before starting on a heavily reviewed product
  • The endpoint takes an item ID, not a product page URL. Passing a URL returns 422
  • Reviewer names and buyer IDs come back in the raw response. Strip them before storage unless you have a reason and a lawful basis to keep them

When not to use this.

If you want the ratings summary alone, the product-details endpoint carries it in one request. Page through reviews when you need the text, the variant link, or the dates.

See the rate card

Other endpoints.

Price your exact scope before you pay.

The rate card is public and an estimate costs nothing.