Search Lazada product listings by keyword across Southeast Asian storefronts, with optional sort, page and price range filters.
View all Lazada Product Search API endpoints →Returns a page of Lazada search results for a keyword on one country storefront. Inputs: keywords (required phrase), site (required storefront code: my, sg, vn, id, ph or th), and optional page, sort (pop, sales, price_up or price_down), price_start and price_end. Observed in a live probe (keywords t shirt, site th, page 1, HTTP 200): a JSON envelope with code 200 and msg success, and a data object with page, page_size (40), start_key, total_count (33,395 in that call), keyword, cat_url, sort, price_start, price_end and an items list of 40 entries. Every probed item carried item_id, product_url, title, img, category_path, brand, brand_id, currency (THB), price, price_info (sale_price, origin_price), discount, review_info (average_score, review_count), comment_count, shop_info (shop_id, shop_name, shop_url, seller_id, seller_name), sold_count, delivery_info (area_from), is_in_stock and is_ad. Unverified: a documentation example also shows a data.extra token that did not appear in the probe, and the other five storefronts, the price filters and page numbers above 1 were not probed. Numeric values such as price, sold_count and comment_count arrive as strings. The result is a snapshot of search listings, not a sales, stock or order feed.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/lazada-api/search-items-by-keywords API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/lazada-api/search-items-by-keywords?key=<API_KEY>&keywords=t+shirt&page=1&site=th&sort=pop'
Query Result
Use Cases
- Cross-country price grid: run one keyword once per site value, keep site and currency on every row, and convert with a dated rate table before naming the cheapest market.
- Price-band sweep: repeat the same keyword with successive price_start and price_end windows and compare total_count per band to see where listings cluster before picking a price point.
- Cross-border sourcing shortlist: sort a keyword with price_up, export the first pages with title, price and shop_info to a sheet, and hand the shop names to a buyer for supplier outreach.
- Daily keyword price snapshot: store site, keyword, item_id, price, currency and fetch time, then diff snapshots to surface price drops on the listings you track.
- Brand minimum-price compliance: search the brand name on each storefront and flag listings priced under the agreed floor, with shop_info attached for follow-up.
- Seller concentration check: group one keyword's result pages by shop_id to see whether a few shops dominate the first pages or supply is fragmented.
- Keyword saturation table: record total_count for candidate product keywords per site as a supply-side proxy (listing count, not demand or sales).
- Shopping-assistant tool call: expose the search as a function so an agent can answer cheapest wireless earbuds in Malaysia under a budget with structured price and currency.
- Outlier-price screening: compare each listing with the median price of its keyword and site to flag suspiciously cheap items for review.
Frequently asked questions
Which Lazada storefronts can I search?
The required site parameter takes one of my (Malaysia), sg (Singapore), vn (Vietnam), id (Indonesia), ph (Philippines) or th (Thailand). Send a single code per request. Only th was exercised in the live probe, so check a sample response before depending on another storefront.
How do I compare the same keyword across countries?
Call the endpoint once per site value with the same keywords. Prices come back in each storefront's own currency (THB in the Thailand probe), so read the currency field on every item and convert with a dated exchange-rate table instead of comparing raw price strings.
How many results come back per page and how do I get more?
The probe returned 40 items with page_size 40 on page 1, alongside total_count (33,395 for t shirt on th). Increase the page parameter to move through the list. Pages above 1 were not probed, so stop when items comes back empty.
What values does sort accept and what is the default?
sort accepts pop, sales, price_up and price_down. When the probe sent no sort value the response reported sort as pop, so popularity ordering appears to be the default. The applied value is echoed in data.sort.
How do price_start and price_end work?
Both are optional numeric strings that bound the listing price, and the response echoes them in data.price_start and data.price_end (empty strings when omitted). The probe did not send them, so test a narrow window on your target storefront and read the bounds in that storefront's currency.
Which fields does each item contain?
In the probe every item had item_id, product_url, title, img, category_path, brand, brand_id, currency, price, price_info (sale_price and origin_price), discount, review_info (average_score and review_count), comment_count, shop_info (shop_id, shop_name, shop_url, seller_id, seller_name), sold_count, delivery_info.area_from, is_in_stock and is_ad.
Are price and count fields numbers or strings?
They are strings. price, comment_count and sold_count were strings in the probe, and a documentation example shows sold_count in an abbreviated form such as 38.1K, so parse it defensively and keep the raw text next to any number you derive.
Does this give sales history, stock levels or order data?
No. It returns a snapshot of search listings. sold_count and comment_count are figures displayed on the listing, is_in_stock is a per-listing flag, and there is no order, inventory or historical sales feed. Store your own timestamps if you need a time series.
What does a successful response look like?
A JSON object with code 200, msg success and a data object holding page, page_size, start_key, total_count, keyword, cat_url, sort, price_start, price_end and items. Check code before reading items. start_key is an opaque value whose role is not documented, so drive paging with the page parameter.