Lazada product data scraping
Returns title, brand, category, images, description, specifications and the item and SKU identifiers. Useful for catalogue enrichment, listing audits and matching your products to reseller listings.
Lazada is built on brand stores, SKU-level pricing and a busy calendar of vouchers and mega-sales. This API converts Lazada product, store and search pages into structured JSON, so brands, sellers and analysts can audit prices, watch SKU stock, score sellers and read customer feedback across six Southeast Asian countries through one REST integration.
# Request (replace the key and link with your own)
POST https://api.webfusiondata.com/v1/product
Authorization: Bearer $WFD_API_KEY
{ "url": "https://www.lazada.sg/products/example-blender-i123456789-s987654321.html",
"country": "SG" }
# Response (sample data, not a live listing)
{
"item_id": "123456789",
"sku_id": "987654321",
"marketplace": "SG",
"title": "Example Personal Blender",
"price": { "amount": 39.90, "currency": "SGD" },
"original_price": 59.90,
"availability": "In stock",
"rating": 4.7,
"seller": { "name": "Example Official Store", "type": "LazMall" }
}
Sample values for illustration only. Exact field names and nesting for your Lazada scope are confirmed in the API reference issued with your key.
Lazada is one of the major online marketplaces in Southeast Asia, where independent sellers sit alongside official brand stores under the LazMall banner. The Lazada Product Data Scraping API reads a product, store or search page and hands it back as JSON. You provide a Lazada link or a keyword and a country, and the response contains named fields such as price, discount, SKU variants, stock, rating and the seller behind the listing.
Lazada pages are organised around SKUs: one item ID can carry several variants, each with its own price and stock level. That makes Lazada data valuable for brands that need to know exactly which colour, size or bundle is being undercut. Our collection layer takes care of page rendering, proxies, bot checks, parsing and validation, so your team receives consistent records instead of raw HTML.
Typical users include brands checking price compliance across resellers, marketplace sellers tracking rivals, and analysts sizing demand in new Southeast Asian countries. Our price monitoring and price intelligence services build on the same data.
Follow a Lazada request from the first call to usable data in six steps.
List the Lazada countries, brand stores, products or keywords you need to follow.
Note whether you need SKU-level prices, seller scores or review text, so the scope is confirmed early.
Put a Lazada product link in url, or use site and query for a search. Set country to match the Lazada site.
Choose /v1/product for one listing, /v1/search for ranked results, /v1/monitor for follow-ups and /v1/bulk for long lists.
Pass your API key as a bearer token in the Authorization header.
Run a few listings through the sandbox to confirm the field names suit your database before going live.
We render the Lazada page, separate item and SKU data, read the seller panel and check each field against its expected type.
Short jobs return at once. Bulk work returns a job ID that you check at /v1/status/:job_id or receive by webhook.
Records arrive as JSON, with CSV or XLSX available for bulk exports. Each one is stamped with crawled_at.
Lazada prices can shift when vouchers or mega-sale events begin, so the capture time is what lets you compare like with like.
Run price compliance reports, rank sellers, mine reviews for product issues or size up a new country.
See Integration and Data Delivery for a compliance-check example.
What the Lazada API can do for pricing, availability, seller and review analysis, and which parts are documented versus agreed per project.
Returns title, brand, category, images, description, specifications and the item and SKU identifiers. Useful for catalogue enrichment, listing audits and matching your products to reseller listings.
One Lazada item can hold many SKU variants. The API returns the price for each variant where the page shows it, so you can compare the exact colour, size or bundle your customers buy.
Tracks price, original price, discount and currency, with scheduled checks and a webhook when a price changes or a campaign discount appears.
Returns in-stock or sold-out status and, where exposed, stock by SKU, so you can catch out-of-stock periods and restocks on rival and reseller listings.
Returns store name, seller type (LazMall or marketplace), seller rating and delivery and chat performance indicators where displayed, so sellers can be ranked on service as well as price.
Returns rating, review count and star breakdown, with review text, date, purchased SKU and seller replies available as a project option for sentiment and quality analysis.
Where a listing shows questions from shoppers and answers from the seller, they can be collected to reveal what information buyers find missing from a product page.
Run keyword searches or collect a rival’s listings, then compare price, discount depth and ratings across every seller of the same product.
Switch country with a single parameter and compare pricing, assortment and seller mix across Lazada’s Southeast Asian sites in local currencies.
The fields returned for Lazada listings, what each one holds and how teams use it. Availability follows what the Lazada page shows for the selected country.
| Data Field | Description | Business Application | Availability |
|---|---|---|---|
item_id / sku_id | Lazada item and SKU identifiers taken from the product link | Product and variant matching | Core |
title | Listing title as shown on the page | Catalogue and listing analysis | Core |
brand / category | Brand and category path | Brand and category benchmarking | Core |
price.amount / price.currency | Current price and the currency of the selected country | Price comparison, compliance checks | Core |
original_price / discount | Crossed-out price and discount percentage | Campaign and markdown analysis | Where displayed |
variants | SKU options such as colour, size or bundle, with price and stock where exposed | SKU-level monitoring | Where displayed |
availability / stock | In-stock or sold-out status, and quantity where exposed | Availability tracking | Core |
rating / review_count | Average rating, star breakdown and number of reviews | Quality benchmarking | Where displayed |
reviews (text) | Review text, stars, date, purchased SKU and seller reply | Sentiment and NLP pipelines | Confirm at onboarding |
questions | Buyer questions and seller answers shown on the listing | Content gap analysis | Confirm at onboarding |
seller.name / seller.type | Store name, and whether it is a LazMall or marketplace seller | Seller segmentation | Where displayed |
seller.rating | Seller positive-rating score | Seller reputation benchmarking | Where displayed |
seller.performance | Shipping-on-time and chat-response indicators | Seller scorecards | Where displayed |
vouchers / shipping | Voucher messages, free-shipping flags, delivery options and ships-from location | Landed-price comparison | Where displayed |
product_url / marketplace | Listing link and the Lazada country site it came from | Reference and validation | Core |
crawled_at | Timestamp of data capture | Freshness checks, time series | Core |
Core = part of the standard field set on our ecommerce API. Where displayed = returned when the Lazada page for that country shows it, so it can be empty for some listings or sellers. Confirm at onboarding = settled per project. Images are also returned. Field names are illustrative; your API reference is the source of truth.
Lazada calls go through the same versioned endpoints as our Ecommerce Scraping API. Lazada-specific parameter names that are not yet published are marked.
| Endpoint | Purpose | Parameters | Expected response |
|---|---|---|---|
POST /v1/productDocumented |
Full record for one Lazada listing: SKU prices, stock, ratings and the seller panel. | Required: urlOptional: country; separate item_id and sku_id fields are a confirm |
One JSON product record, returned synchronously. |
POST /v1/searchDocumented |
Run a Lazada keyword or brand search and return the ranked results with price, rating and store. | Required: site ("lazada"), queryOptional: country |
JSON with query, result_count and a results array. |
POST /v1/monitorDocumented |
Follow a listing and receive a webhook when its price, stock or discount changes. | Required: urlOptional: webhook URL and check frequency names: confirm |
A monitor ID you use to read tracked data later. |
GET /v1/monitor/:idDocumented |
Read the current values and change log for a followed listing. | Required: id (path) |
JSON with the latest values and recorded changes. |
POST /v1/bulkDocumented |
Submit many Lazada links at once, such as every reseller listing of your product, for background processing. | Required: list of URLs Optional: delivery destination and format (JSON, CSV or XLSX) names: confirm |
A job ID, then results via webhook or storage export. |
GET /v1/status/:job_idDocumented |
State and progress of an asynchronous crawl or bulk export. | Required: job_id (path) |
JSON with job state and progress. |
| Situation | Typical HTTP status | How to fix it |
|---|---|---|
| Missing or malformed Lazada link | 400 | Send a full product link, including https://, on a Lazada country domain. |
| Country and domain disagree | 400 / 422 | Use the matching country code, for example MY for lazada.com.my or PH for lazada.com.ph. |
| Missing or invalid API key | 401 | Send Authorization: Bearer <key> and check the key belongs to the right environment (sandbox or live). |
| Listing removed or SKU unavailable | 404 or an empty record | Lazada listings can be taken down or a SKU withdrawn. Check the link still opens, then retry or remove it from your list. |
| Request limit exceeded | 429 | Wait, then retry with backoff. Response headers show your remaining quota for the window. |
| Temporary processing failure | 5xx | Retry with exponential backoff, and use /v1/bulk for large lists instead of many synchronous calls. |
Status codes follow common REST conventions (429 is the one shown in our published dashboard example). The exact codes and error bodies are listed in the API reference supplied with your key.
Two typical Lazada calls and the JSON they return. Illustrative sample data — not live marketplace information.
curl -X POST https://api.webfusiondata.com/v1/product \
-H "Authorization: Bearer $WFD_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://www.lazada.sg/products/example-blender-i123456789-s987654321.html",
"country": "SG"
}'
curl -X POST https://api.webfusiondata.com/v1/search \
-H "Authorization: Bearer $WFD_API_KEY" \
-d '{"site": "lazada", "query": "rice cooker", "country": "MY"}'
url or site + query choose what to fetch, and country picks the Lazada site. Keep the key in an environment variable — never hard-code it or expose it in client-side code.{
"item_id": "123456789",
"sku_id": "987654321",
"marketplace": "SG",
"title": "Example Personal Blender",
"brand": "Example Brand",
"price": { "amount": 39.90, "currency": "SGD" },
"original_price": 59.90,
"discount": { "percent": 33 },
"availability": "In stock",
"rating": 4.7,
"review_count": 312,
"seller": {
"name": "Example Official Store",
"type": "LazMall",
"rating": 96
},
"crawled_at": "2026-01-15T09:30:00Z"
}
{
"query": "rice cooker",
"result_count": 40,
"results": [
{ "title": "Example Rice Cooker 1.8L", "price": 129.00,
"rating": 4.6, "seller_type": "LazMall" }
]
}
Search results are a lighter record than the product call, so use /v1/product when you need SKU variants, stock and seller detail. The final Lazada schema is confirmed in your API reference.
Lazada operates a dedicated site in each Southeast Asian country, with its own currency, language and seller base. Choose one with the country parameter. We do not claim coverage beyond what is confirmed at onboarding.
| Country | Lazada domain | Local currency | Status for the API |
|---|---|---|---|
| Singapore | lazada.sg | SGD | Confirm at onboarding |
| Malaysia | lazada.com.my | MYR | Confirm at onboarding |
| Thailand | lazada.co.th | THB | Confirm at onboarding |
| Indonesia | lazada.co.id | IDR | Confirm at onboarding |
| Philippines | lazada.com.ph | PHP | Confirm at onboarding |
| Vietnam | lazada.vn | VND | Confirm at onboarding |
This is a reference list of Lazada’s Southeast Asian sites, not a coverage guarantee. Need a different region? Tell us and we will confirm feasibility.
Why it matters: big shopping moments such as 11.11 and 12.12 run across several countries at once, so capture each market on the same day if you want fair comparisons. Convert currencies to a single base before comparing price levels, and tell us if you need titles translated or categories mapped to one taxonomy for regional reporting.
What is published today, and what we confirm in writing before you go live. We do not publish numeric limits, latency or uptime figures on this page.
| Topic | How it works | Status |
|---|---|---|
| Authentication | Send your API key as a bearer token in the Authorization header, and use the sandbox key while you test. | Documented |
| Limits and concurrency | Per-minute limits and concurrent requests follow your plan, and response headers show remaining quota. Mega-sale weeks bring heavier monitoring, so agree volumes beforehand and use /v1/bulk for large lists. | DocumentedNumbers: your plan |
| Validation and errors | Malformed or missing parameters return a standard HTTP error (see Endpoints), and every response is schema-checked before delivery. | Exact codes: API reference |
| Timeouts and retries | Use a client timeout and retry reads on 429 and 5xx with exponential backoff. Send long jobs to /v1/bulk and check /v1/status/:job_id, and avoid blind retries of POST /v1/monitor or /v1/bulk. | Recommended practice |
| Pagination | Search returns a result_count and a result list. The depth available for broad keywords is agreed per project. | Confirm at onboarding |
| Usage monitoring | An account dashboard shows request volume, latency, success rate and job status. | Documented |
Wire Lazada data into a price-compliance report, a seller scorecard or a regional dashboard. The recipe stays the same: a request layer, a place for results and a schedule.
Agree countries, brand stores or products, fields and refresh rate, then try a handful of listings in the sandbox.
Centralise authentication, timeouts and retries so every Lazada job behaves the same way.
Store price, seller type and stock per item, SKU and country with each crawled_at, so you can show how prices moved around a campaign.
Follow priority listings with monitors, run bulk checks on reseller lists and send webhooks into your alerting tools.
import os, requests
API = "https://api.webfusiondata.com/v1/product"
HEADERS = {"Authorization": f"Bearer {os.environ['WFD_API_KEY']}"}
MIN_PRICE = 35.00
LINKS = [
"https://www.lazada.sg/products/example-blender-i123456789-s987654321.html",
]
def fetch(url, country="SG"):
r = requests.post(API, json={"url": url, "country": country},
headers=HEADERS, timeout=60)
r.raise_for_status()
return r.json()
for url in LINKS:
p = fetch(url)
price = p["price"]["amount"]
if price < MIN_PRICE:
seller = p.get("seller", {}).get("name", "unknown")
print(f"Below minimum: {seller} at {price} {p['price']['currency']}")
The default format for every endpoint.
Bulk results for reseller lists or search runs, delivered as CSV or XLSX to S3, GCS or your own bucket.
Callbacks when a job completes or a followed price, stock or discount changes, plus recurring checks through /v1/monitor.
Managed warehouse connectors, client libraries and no-code options.
Listed on the Ecommerce Scraping API page; availability for your Lazada scope is confirmed during onboarding. See also the AI Parser and ecommerce datasets. Related: product availability and MAP monitoring.
It is a REST API from WebFusion Data that returns structured JSON for Lazada listings, stores and search results. You send a Lazada link or a keyword plus a country and receive fields such as price, discount, SKU variants, stock, rating and seller details. It shares endpoints and infrastructure with our Ecommerce Scraping API, so you do not operate proxies, browsers or parsers yourself.
Core fields include item and SKU IDs, title, brand, category, price and currency, availability, images, listing link, country site and a capture timestamp. Original price, discount, variants, rating, review count, seller details, vouchers and shipping are returned where the page displays them. Review text and buyer Q&A are agreed per project. The data fields table lists each one.
Yes, through the product link. Lazada product links carry an item ID and a SKU ID, so you can build the link from those values and submit it to /v1/product with the matching country. Both IDs come back in the response for matching. Whether dedicated item_id and sku_id parameters are available is confirmed at onboarding.
Register a listing with POST /v1/monitor and we check it on a schedule, sending a webhook when price, discount or stock changes. GET /v1/monitor/:id returns the latest values and the change log. Check frequency is scoped to your project, and history begins when you register a listing, so keep each crawled_at timestamp if you want your own long-term series.
Availability status is returned for each listing, and stock by SKU is included where Lazada shows it. Teams use this to catch out-of-stock periods, watch restocks and see when a reseller runs short on a specific colour or size. Quantity figures depend on what the page displays, so some listings return status only.
Where displayed, you receive the store name, whether the seller is LazMall or a marketplace shop, seller rating and delivery and chat indicators. Combined with price and discount data, this lets you rank sellers by reliability, separate official stores from resellers and find who is undercutting your list price. The exact indicator list is confirmed for your scope.
Rating, star breakdown and review count are returned where displayed. Review text, date, purchased SKU and seller replies can be scoped as a project option, and buyer questions and answers can be collected where a listing shows them. We collect only publicly visible content, and whether review images are included is confirmed at onboarding.
We do not claim blanket coverage. The country parameter selects the site, and the Lazada countries available to you, such as Singapore, Malaysia, Thailand, Indonesia, the Philippines and Vietnam, are confirmed during onboarding. Tell us which markets you need and we will confirm each one. See supported country sites.
Submit your product listings and reseller links through /v1/bulk or follow them with monitors, then compare each seller’s price with your minimum advertised price. The seller name and type in each record show who is below the line and whether they are an official store. Our MAP monitoring service can run this as a managed workflow.
Use the Request API Demo button or the form below and tell us the countries, products or stores, fields, refresh frequency and delivery format you need. We confirm the scope and set up access with a sandbox. Requests use a bearer token and return JSON, with CSV or XLSX for bulk exports. You can also email sales@webfusiondata.com or book a consultation.

At WebFusionData, we specialize in cutting-edge web scraping solutions to help you unlock valuable insights and drive business growth. Whether you need custom data extraction, real-time monitoring, or large-scale web scraping, our team is here to assist you.
Ready to get started? Contact us for a personalized quote.