Give dealer website URLs, get the vehicles each dealer currently lists for sale on its own website, one row per vehicle (VIN, year, make, model, trim, price, mileage, specs, dealer location, link) plus one status row per dealer. Covers franchise and independent car dealers on 21 website platforms, RV dealers on Interact RV, Inventrue and Coast Technology, truck dealers on iManPro, the DriveTime, Camping World, Rush, SelecTrucks, Ryder, Velocity and TEC chains, and other sites that publish standard schema.org vehicle data. Data comes from the dealers' own public websites; this app is not an official product of any dealer or website provider
Lazada Category Products
Give a Lazada category list URL and an expected count to get public products, prices, brands, shops, and list ranks.
Overview
Category lists are where shoppers first see which Lazada products occupy a niche: the title, the list price, the brand, the shop, and how high the listing sits when the page is ordered by sales. This app turns one public Lazada category list link into a structured table of those products so assortment, pricing, and shop-share work can start from the same list a customer would browse.
Each row keeps the category URL, category name, and list rank beside the product, so later comparisons stay attached to the list that produced them. It is a category-list workbook, not a substitute for a full product page.
Data notes
Each row is one public product from a Lazada category list page. Rows follow the list's sales ranking. Price is the list-page text as returned, without a separate currency code; it belongs to the marketplace of the category URL and is not a normalized number. Rating count is also returned as text. Sales count is a number when the list shows it. Collected at is returned without a timezone. Collect timestamp and Created timestamp are millisecond Unix values from the source record. Listing status is the source text as returned, even when that text is not in English. Business ID, Category URL, and Source item repeat the list context across rows from the same request.
The collection does not cover product-detail pages, variants, reviews, orders, or seller-backend data, and it does not include listings that are not visible on the public category list. A No-data marker distinguishes a list item that produced no products from ordinary product rows.
What a result looks like
Each row is one product from a public Lazada category list.
| Product ID | Product title | Price | Sales count | Shop name | List rank |
|---|---|---|---|---|---|
| 5065024768 | [Bpom] Pinkflash # Ohmykiss Matte Liquid Lipstick Lip Tint Waterproof Soft Long Lasting Moisturizing High Pigmentation Lipstick 21 Colors | 23900 | 510300 | PINKFLASH | 1 |
| 7371320783 | IMPLORA Urban Lip Cream Matte Lip Velvet ( lipcream Lipstick Lipstik ) (BPOM) | 19700 | 214600 | Fufumise | 2 |
Brand, Category, Rating count, and Image URL are also available when the list shows them.
Use cases
- For assortment checks, group rows by Category and scan Product title with Product ID to see which products occupy a list.
- For list-price comparison, rank Price against Sales count and Brand to see which cards look like volume leaders versus niche listings.
- For shop-share work, group Shop name and Shop ID, then read List rank and Price to see which shops occupy the top of a sales-ranked category list.
- For catalog hygiene, read Listing status with No-data marker to separate ordinary product rows from list items that returned nothing.
Scope and boundaries
One Lazada category list URL per task with an expected product count from 1 to 2400; results are returned in complete batches of 80 and may be rounded up; fetch protection covers up to 30 pages or 2400 records; coverage is limited to public category-list products.
- Good for
- When you need public products from a Lazada category list page.
- When you need to compare category products by price, brand, shop, and sales rank.
- Do not use for
- When you need a product detail page, variants, reviews, or price history — this App only returns category-list fields.
- When you need orders, seller-backend, or non-public catalog data — this App covers publicly visible listings only.
Failure handling
Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.
- 1If no products are returned, confirm the category list URL is publicly accessible and actually contains products, then resubmit.
- 2Keep completed product rows after a partial success; resubmit the same input after a failed or expired task.
- 3Retry later after rate limiting, temporary unavailability, or a timeout.
- 4If authentication fails, verify the API Key configured for the execution environment.
Input
Parameters required to call this App, generated from the input.schema in manifest.json.
- Lazada category list URL
itemRequiredstringA full HTTPS Lazada category list page URL. The link should point to a publicly accessible category list; results belong to that site's catalog.Examplehttps://www.lazada.co.id/catalog/?q=Makeup%20Bibir - Expected product count
crawl_countRequiredstringExpected number of products to collect, from 1 to 2400. Results are returned in complete batches of 80, so the actual count may be rounded up. A shortfall still bills as 80 records.Example2
Output
Field structure of a single record, generated from the output.schema in manifest.json.
- Business ID
biz_idstringBusiness identifier associated with the record; in the current data shape this is the category list URL.Examplehttps://www.lazada.co.id/catalog/?q=Makeup%20Bibir - Brand
brand_namestringBrand name shown for the product on the category list.ExamplePINKFLASH - Category ID
category_idstringCategory identifier path as returned; it may contain more than one ID separated by commas.Example3534,3537 - Category
category_namestringCategory name shown on the source list.ExampleMakeup Bibir
Sample data
Generated from output.schema. Fields without a sample value use structural placeholders.
{
"biz_id": "https://www.lazada.co.id/catalog/?q=Makeup%20Bibir",
"brand_name": "PINKFLASH",
"category_id": "3534,3537",
"category_name": "Makeup Bibir",
"collect_time": 1788518168405,
"crawl_time": "2026-09-04T18:36:08",
"created_at": 1788518168405,
"image_url": "https://id-live-01.slatic.net/p/73a5f4e505b1fb08b85d59c3ac5480b5.jpg",
"item": "https://www.lazada.co.id/catalog/?q=Makeup%20Bibir",
"page_num": "1",
"platform_code": "lazada",
"price": "23900",
"product_title": "[Bpom] Pinkflash # Ohmykiss Matte Liquid Lipstick Lip Tint Waterproof Soft Long Lasting Moisturizing High Pigmentation Lipstick 21 Colors",
"rank_index": 1,
"rating_count": "81978",
"sale_count": 510300,
"shop_id": "400610364026",
"shop_name": "PINKFLASH",
"spu_id": "5065024768",
"status_code": "有效",
"source_item": "https://www.lazada.co.id/catalog/?q=Makeup%20Bibir",
"no_data": false
}Integration
This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.
With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.
Client config
Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=hello_moto/lazada-category",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Let AI set it up for you
Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (By default it guides you through signing in, and never asks you to send your API key in the chat.)
detail.access.mcp.composeHint
Pricing
Charged once per submitted run, regardless of how many records are returned.
Charged by the number of records successfully returned. Failed runs are not charged. Billed in units of 80 records; any partial unit is rounded up to 80 records.
Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.
View creditsTry it now
Fill in the parameters and run. Results come from a real call.