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.
Original · en-USVolver a la traducción
Descripción general
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.
Alcance y límites
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.
- Adecuada para
- 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.
- No usar para
- 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.
Gestión de fallos
Comportamiento de fallos y reintentos declarado por el desarrollador. Recomendamos incluirlo en tu prompt del sistema al integrar.
- 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.
Entrada
Parámetros necesarios para llamar a esta App, generados a partir del input.schema del manifest.json.
- Lazada category list URL
itemObligatoriostringA full HTTPS Lazada category list page URL. The link should point to a publicly accessible category list; results belong to that site's catalog.Ejemplohttps://www.lazada.co.id/catalog/?q=Makeup%20Bibir - Expected product count
crawl_countObligatoriostringExpected 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.Ejemplo2
Salida
Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.
- Business ID
biz_idstringBusiness identifier associated with the record; in the current data shape this is the category list URL.Ejemplohttps://www.lazada.co.id/catalog/?q=Makeup%20Bibir - Brand
brand_namestringBrand name shown for the product on the category list.EjemploPINKFLASH - Category ID
category_idstringCategory identifier path as returned; it may contain more than one ID separated by commas.Ejemplo3534,3537 - Category
category_namestringCategory name shown on the source list.EjemploMakeup Bibir
Datos de ejemplo
Generado a partir de output.schema. Los campos sin valor de ejemplo usan marcadores de estructura.
{
"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
}Integración
Esta App se puede integrar mediante MCP, API, SDK o exportación de archivos — todos los canales comparten las mismas capacidades y precios. Cada solicitud se autentica con la cabecera Authorization: Bearer usando una API Key (de larga duración, creada en la consola de Data Hub); los clientes MCP también pueden iniciar sesión con OAuth sin clave. Más opciones como CLI y Skill están en camino. Esta App se ejecuta de forma asíncrona y se puede cancelar a mitad de camino: Tras la cancelación, la ejecución se detiene. Los registros ya entregados se conservan y se facturan.
Con MCP (Model Context Protocol) puedes llamar a esta App directamente desde clientes de IA como Claude y Cursor. Elige tu cliente y el modo de autenticación, y copia la configuración de abajo.
Configuración del cliente
Sustituye el valor tras Bearer por tu API Key de larga duración. Funciona en cualquier cliente, CI o entorno sin interfaz.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=hello_moto/lazada-category",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Deja que la IA lo configure por ti
¿No quieres editar configuraciones a mano? Copia el prompt de instalación y pégalo en cualquier cliente de IA: completará la configuración a su manera. (De forma predeterminada te guía para iniciar sesión y nunca te pide que envíes tu API Key en el chat.)
detail.access.mcp.composeHint
Precios
Se cobra una vez por cada ejecución enviada, independientemente del número de registros devueltos.
Se cobra según el número de registros devueltos correctamente. Las ejecuciones fallidas no se cobran. Se factura en unidades de 80 registros; cualquier unidad parcial se redondea a 80 registros.
Los distintos eventos de facturación se acumulan de forma independiente. Consulta cada elemento para más detalles. Las ejecuciones fallidas no se cobran.
Ver créditosPruébalo ahora
Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.