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
Rakuten Product Details
Give a list of Rakuten product page URLs and get title, product ID, shop, listing status, and SKU details
Original · en-USVolver a la traducción
Descripción general
Rakuten Product Details turns known Japanese product pages into one snapshot row per listing: title, product ID, shop, listing status, SKU text, and the page URL. Catalog and competitive-intelligence teams can compare Rakuten listings without opening each page.
The value is the product-page snapshot itself. Title, listing status, and SKU text stay in the source language, price strings inside SKU details keep their original numbers, 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 Rakuten product page at collection time. Rows are deduplicated by the submitted product URL. Listing status and URL status are the page values recorded at collection time, not a live checkout state. SKU details stay as original source text, including price strings; the source does not state a currency. Collection time is stored as the source provided it and has no timezone. Created timestamp and Updated timestamp are Unix milliseconds.
Only public product pages that can be reached from a complete Rakuten product URL are covered. Unavailable or invalid pages can still appear as rows with the No-data flag set. Search results, reviews, sales history, and live inventory are not included.
What the results look like
Each record is one Rakuten product snapshot at collection time:
| Product ID | Shop ID | Listing status | Product URL | SPU ID |
|---|---|---|---|---|
| 10005020 | 406191 | 在售 | https://item.rakuten.co.jp/alice00/19rdv6003/ | 19rdv6003 |
| 10000405 | 346082 | 在售 | https://item.rakuten.co.jp/store-ecovacs-japan/dkx55-12ee/ | dkx55-12ee |
The result also includes Business ID, Submitted URL, Product title, Main image, SKU details, Collection time, Updated timestamp, URL status, and No-data flag.
Use cases
- For catalog building, file Product ID, Product title, and Shop ID, and use Collection time to judge how fresh the snapshot is.
- For competitive review, group by Shop ID and compare Product title, Listing status, and URL status.
- For spec and price extraction, read SKU details and check Submitted URL with No-data flag to see which pages resolved.
Alcance y límites
Submit at most 200 Rakuten product page URLs per run. Each URL returns one detail row or a no-data flag. Results are returned in a stable collection-time order. The app does not filter, aggregate, or custom-sort business fields.
- Adecuada para
- When you need titles, product IDs, shops, listing status, and SKU details for a batch of known Rakuten product pages
- When you want to keep product URLs, main images, and SKU 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 reviews, sales history, or historical prices — this app only returns a product-detail snapshot
- When you need live checkout prices or live inventory — listing status and SKU prices 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 that the product page URL is complete and still publicly available
- 2If the run hits a rate limit, request timeout, or temporary service error, retry later with the same URL 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 page URLs
itemsObligatorioarray<object>Rakuten product pages to collect details for. Each entry is one complete product page URL. You can submit 1 to 200 items.Cantidadhasta 200 elementosEjemplo[{"item":"https://item.rakuten.co.jp/alice00/19rdv6003/"}]
Salida
Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.
- Business ID
biz_idstringBusiness identifier for the Rakuten product-detail record, usually the product page URLEjemplohttps://item.rakuten.co.jp/alice00/19rdv6003/ - Review count
comment_countstringReview count text shown on the product pageEjemplo0 - Collection time
crawl_timestringCollection time text for the product snapshot; the source value has no timezoneEjemplo2026-09-14T11:34:55 - Created timestamp
created_atintegerUnix millisecond timestamp when the record was createdEjemplo1789356895498
Datos de ejemplo
Generado a partir de output.schema. Los campos sin valor de ejemplo usan marcadores de estructura.
{
"biz_id": "https://item.rakuten.co.jp/alice00/19rdv6003/",
"comment_count": "0",
"crawl_time": "2026-09-14T11:34:55",
"created_at": 1789356895498,
"item": "https://item.rakuten.co.jp/alice00/19rdv6003/",
"job_type": "BasicInfo",
"main_image_url": "<main_image_url>",
"platform_code": "rakuten",
"product_id": "10005020",
"product_title": "Anker Soundcore Liberty 5 Pro Max 完全ワイヤレスイヤホン Bluetooth 6.1 ノイズキャンセリング LDAC ハイレゾ Dolby Atmos AIボイスレコーダー",
"product_url": "https://item.rakuten.co.jp/alice00/19rdv6003/",
"shop_id": "406191",
"skus": "[{\"discount\": null, \"images\": null, \"originalPrice\": \"34500.0\", \"price\": \"34500.0\", \"skuId\": \"19rdv6003-00\", \"skuName\": \"ミッドナイトブラック\"}, {\"discount\": null, \"images\": null, \"originalPrice\": \"34500.0\", \"price\": \"34500.0\", \"skuId\": \"19rdv6003-01\", \"skuName\": \"シャンパンゴールド\"}]",
"source_name": "rakuten_detail_202609",
"spu_id": "19rdv6003",
"status_code": "在售",
"task_item": "https://item.rakuten.co.jp/alice00/19rdv6003/",
"no_data": false,
"updated_at": 1789356895498,
"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/rakuten-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.