Lazada APIlazada.sg ↗
Access Lazada.sg product listings, reviews, seller profiles, category browsing, and stock snapshots via 7 structured API endpoints.
What is the Lazada API?
The Lazada Singapore API gives developers structured access to Lazada.sg across 7 endpoints, covering product search, full product details, customer reviews, seller catalogs, category browsing, flash sale recommendations, and live store stock snapshots. The search_products endpoint alone returns up to 40 products per page with fields including price, ratingScore, sellerName, brandName, and location, giving you a solid starting point for price monitoring or catalog aggregation.
curl -X GET 'https://api.parse.bot/scraper/116c43fb-4f92-4a6d-8ab1-03b7a7b6a6dc/search_products?page=1&sort=priceasc&query=laptop' \ -H 'X-API-Key: $PARSE_API_KEY'
Full-text search over Lazada.sg product listings. Returns a paginated list of products matching the query keyword, with pricing, ratings, seller info, and images. Supports sort ordering. Each page returns up to 40 products.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination |
| sort | string | Sort order for results |
| queryrequired | string | Search keyword (e.g. 'laptop', 'headphones', 'iphone') |
{
"type": "object",
"fields": {
"total": "integer total number of matching products",
"products": "array of product objects with name, itemId, price, ratingScore, sellerName, image, location, brandName"
},
"sample": {
"data": {
"total": 4080,
"products": [
{
"name": "HP 14 Inch Laptop",
"image": "https://sg-live-01.slatic.net/p/c10910dc54223d302907c47b7c2d4568.jpg",
"price": "109",
"itemId": "1993294711",
"review": "87",
"inStock": true,
"location": "Singapore",
"sellerId": "1000026206",
"brandName": "HP",
"priceShow": "$109.00",
"sellerName": "Reboot SG",
"ratingScore": "4.409090909090909"
}
]
},
"status": "success"
}
}About the Lazada API
Product Search and Details
The search_products endpoint accepts a required query string plus optional page and sort parameters, returning a total count and an array of product objects. Each object carries itemId, name, price, ratingScore, sellerName, brandName, image, and location. The itemId value is the key that unlocks the other endpoints. Pass it to get_product_details to retrieve SKU-level specifications, a seller object (including sellerId, shopId, store tags, and ratings), delivery options, warranty info, and a tracking metadata block containing the product's name, price, brand, and category.
Reviews and Seller Data
get_product_reviews paginates 5 reviews per page and returns each review's buyerName, rating, reviewContentList, reviewTime, mediaList (attached photos or video), and any seller reply. The response also includes totalItems, totalPages, and an impressionTags array summarising tag-level sentiment. For seller-focused workflows, get_seller_products lists all products in a store at 20 items per page; it requires both seller_id and shop_id (both available from upstream endpoints) and returns title, price, discountPrice, rating, reviews, inStock, and imageUrl per item.
Category Browsing and Recommendations
get_category_listings accepts a category_slug with or without the shop- prefix and returns listItems (same shape as search results), a filter object with brand, category, and service options, sortBar options, and a breadcrumb array for navigation context. get_flash_sale_products requires no input and returns the Lazada homepage recommendation feed — useful for tracking featured products and promotional pricing over time.
Live Stock Snapshots
get_store_stock_snapshot takes a comma-separated item_ids string plus seller_id and shop_id, and returns one row per item with availability status. An optional keyword narrows the store catalog request, and an optional sku_ids string maps caller-supplied SKU IDs to each row. The response includes complete (whether all items were found), coverage_truncated (whether the store catalog exceeded 100 rows), missing_ids, rows_returned, store_total_matches, and applied_filters. Note that source_as_of and cache_age_seconds are always null because the store catalog publishes no timestamp.
The Lazada API is a managed, monitored endpoint for lazada.sg — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when lazada.sg changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official lazada.sg API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Monitor competitor pricing on Lazada.sg by polling
search_productsfor specific keywords and trackingpriceover time. - Aggregate customer sentiment by pulling
reviewsandimpressionTagsfromget_product_reviewsacross multiple product IDs. - Build a seller intelligence dashboard using
get_seller_productsto track a store's full catalog, stock status, and discount depth. - Check real-time availability for a watchlist of items using
get_store_stock_snapshotwith comma-separateditem_ids. - Populate a product comparison tool with SKU-level
specificationsand delivery options fromget_product_details. - Track category-level assortment and available brand filters via
get_category_listingsfor market research. - Identify featured and promoted products by recording the
get_flash_sale_productsrecommendation feed on a schedule.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Lazada have an official public developer API?+
What does `get_store_stock_snapshot` actually return, and when is `complete` false?+
complete is false when the store catalog returned more rows than the single request could cover (capped at 100 rows per call). In that case coverage_truncated is true and store_total_matches tells you the full catalog size. Any item IDs that could not be matched appear in missing_ids. The applied_filters object echoes exactly what was sent upstream, including the optional keyword filter.How many reviews does `get_product_reviews` return per page, and what media data is included?+
mediaList, which carries attached image or video URLs uploaded by the buyer. The response also includes totalItems and totalPages so you can iterate to collect the full review set.Does the API cover Lazada storefronts in other Southeast Asian countries such as Thailand, Indonesia, or Malaysia?+
Does the API expose seller vouchers, bundle deals, or promotional coupon data?+
price, discountPrice), ratings, stock status, and specifications, but voucher or coupon metadata is not part of any response schema. You can fork the API on Parse and revise get_product_details to add that endpoint if the data is accessible on the product page.