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
Coupang Product Details
Give Coupang product page URLs and get title, main image, SKU list, listing status, and review count
Original · en-USVolver a la traducción
Descripción general
Coupang Product Details turns known product page URLs into one snapshot row per listing: title, main image, SKU list, listing status, review count, and the page URL. Catalog, pricing, and competitive-intelligence teams can compare Coupang listings without opening each product page.
The value is the listing-page snapshot itself. SKU price numbers stay as they appeared on the page, titles stay in the listing language, and the URL you submitted sits on the same row as the no-data flag so you can see which targets resolved.
Data notes
Each record is a product-detail snapshot taken from the public Coupang product page at collection time. Rows are deduplicated by the submitted product page URL. The SKU list is original text with option names, image links, discount text, and price numbers shown on the page; it is not a converted checkout total, and the source does not state a currency. Collection time and millisecond timestamps are stored as the source provided them; the source does not state a timezone. Listing status and URL status keep the original page text.
Only public product pages that can be reached from a Coupang product URL are covered. Unavailable or invalid products can still appear as rows with the No data flag set. Search results, review text, sales history, and live checkout inventory are not included.
What the results look like
Each record is one Coupang product snapshot:
| Query item | Product title | Listing status | Review count | No data |
|---|---|---|---|---|
| https://www.coupang.com/vp/products/4337552642 | PS5 PULSE Elite 무선 헤드셋 / 한국 정식발매 / 새상품 | 在售 | 1 | No |
| https://www.coupang.com/vp/products/5123987641 | LocknLock 밀폐용기 세트 | 在售 | 128 | No |
The result also includes Main image, Product URL, Product ID, SKU list, URL status, and Collection time.
Use cases
- For catalog building, file Query item, Product title, Main image, and Product URL, and use Collection time to judge how fresh the snapshot is.
- For price and option checks, read SKU list with Listing status to compare option names and page prices without mixing unavailable listings.
- For demand signals, group Product title by Review count to see which listings attract more feedback.
- For URL cleanup, combine URL status, No data, and Product URL to drop invalid or empty targets before the next catalog pass.
Alcance y límites
Submit at most 200 Coupang product page URLs per run. Each URL returns at most one detail row or a no-data flag. The app does not filter, aggregate, or custom-sort business fields.
- Adecuada para
- When you need titles, main images, SKU options, listing status, and review counts for a batch of known Coupang products
- When you want to keep product URLs and SKU price text for later catalog or competitive analysis
- No usar para
- When you need to discover products by keyword — this app only returns details for known product page URLs
- When you need review text, sales history, or historical prices — this app only returns a product-detail snapshot
- When you need live checkout prices or live inventory — price and status are the page values recorded at collection time
Gestión de fallos
Comportamiento de fallos y reintentos declarado por el desarrollador. Recomendamos incluirlo en tu prompt del sistema al integrar.
- 1If a row is marked as no data, check the product page URL and whether the listing is still publicly available
- 2If the run hits a rate limit, request timeout, or temporary service error, retry later with the same product list
- 3If authentication fails, the task context does not match, or the task has expired, do not retry as-is; check the execution credentials or submit a new run
- 4If the task partially succeeds, completed product rows are still returned; failed and no-data counts are visible from the task status
Entrada
Parámetros necesarios para llamar a esta App, generados a partir del input.schema del manifest.json.
- Product list
product_itemsObligatorioarray<object>Coupang product pages to collect details for. Submit 1 to 200 product page URLs; each entry is one URL such as https://www.coupang.com/vp/products/4337552642. Actual results stay within the number submitted, with at most one row per URL.Cantidadhasta 200 elementosEjemplo[{"item":"https://www.coupang.com/vp/products/4337552642"}]
Salida
Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.
- Business ID
biz_idstringOriginal business identifier stored on the product record, usually the product page URL.Ejemplohttps://www.coupang.com/vp/products/4337552642 - Collection time
crawl_timestringOriginal collection timestamp stored with the snapshot.Ejemplo2026-09-15T11:44:58 - Created at
created_atintegerMillisecond timestamp when the record was created.Ejemplo1789443898610 - Source URL
itemstringProduct page URL stored on the product-detail record.Ejemplohttps://www.coupang.com/vp/products/4337552642
Datos de ejemplo
Generado a partir de output.schema. Los campos sin valor de ejemplo usan marcadores de estructura.
{
"biz_id": "https://www.coupang.com/vp/products/4337552642",
"crawl_time": "2026-09-15T11:44:58",
"created_at": 1789443898610,
"item": "https://www.coupang.com/vp/products/4337552642",
"job_type": "BasicInfo",
"main_image_url": "https://image.coupangcdn.com/image/vendor_inventory/98a7/4954c7c54d8a4e4698f86bcf8afea585237180a41f554a95fbe227f5fd53.png",
"platform_code": "coupang",
"product_id": "4337552642",
"product_title": "PS5 PULSE Elite 무선 헤드셋 / 한국 정식발매 / 새상품",
"product_url": "https://www.coupang.com/vp/products/4337552642",
"sku_list": "[{\"discount\": \"22\", \"images\": [\"https://image.coupangcdn.com/image/vendor_inventory/98a7/4954c7c54d8a4e4698f86bcf8afea585237180a41f554a95fbe227f5fd53.png\"], \"originalPrice\": \"298000\", \"price\": \"230000\", \"skuId\": \"21725431452\", \"skuName\": \"PS5 PULSE Elite 무선 헤드셋 / 한국 정식발매 / 새상품\"}]",
"spu_id": "4337552642",
"status_code": "在售",
"task_item": "https://www.coupang.com/vp/products/4337552642",
"no_data": false,
"total_review_count": "1",
"updated_at": 1789443899394,
"url_status": "有效"
}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=super_ig/coupang-product-detail",
"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.
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.