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
Source · en-USRevenir à la traduction
Aperçu
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.
Périmètre et limites
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.
- Adapté pour
- 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
- À ne pas utiliser pour
- 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
Gestion des échecs
Comportement en cas d'échec et de nouvelle tentative déclaré par le développeur. Nous vous recommandons de l'inclure dans votre prompt système lors de l'intégration.
- 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
Entrée
Paramètres requis pour appeler cette App, générés à partir de l'input.schema du manifest.json.
- Product page URLs
itemsRequisarray<object>Rakuten product pages to collect details for. Each entry is one complete product page URL. You can submit 1 to 200 items.Nombrejusqu'à 200 élémentsExemple[{"item":"https://item.rakuten.co.jp/alice00/19rdv6003/"}]
Sortie
Structure des champs d'un enregistrement, générée à partir de l'output.schema du manifest.json.
- Business ID
biz_idstringBusiness identifier for the Rakuten product-detail record, usually the product page URLExemplehttps://item.rakuten.co.jp/alice00/19rdv6003/ - Review count
comment_countstringReview count text shown on the product pageExemple0 - Collection time
crawl_timestringCollection time text for the product snapshot; the source value has no timezoneExemple2026-09-14T11:34:55 - Created timestamp
created_atintegerUnix millisecond timestamp when the record was createdExemple1789356895498
Exemple de données
Généré à partir d'output.schema. Les champs sans valeur d'exemple utilisent des espaces réservés structurels.
{
"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": "有效"
}Intégration
Cette App peut être intégrée via MCP, API, SDK ou export de fichiers — tous les canaux partagent les mêmes capacités et la même tarification. Chaque requête s'authentifie avec l'en-tête Authorization: Bearer à l'aide d'une API Key (longue durée, créée dans la console Data Hub) ; les clients MCP peuvent aussi se connecter via OAuth, sans clé. D'autres options comme la CLI et Skill arrivent bientôt. Cette App s'exécute de manière asynchrone et peut être annulée en cours de route : Après l'annulation, l'exécution s'arrête. Les enregistrements déjà livrés sont conservés et facturés.
Avec MCP (Model Context Protocol), vous pouvez appeler cette App directement depuis des clients IA comme Claude et Cursor. Choisissez votre client et votre mode d'authentification, puis copiez la config ci-dessous.
Config du client
Remplacez la valeur après Bearer par votre API Key longue durée. Fonctionne dans n'importe quel client, en CI ou en environnement sans navigateur.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=super_ig/rakuten-product-detail",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Laissez l'IA tout configurer pour vous
Vous ne voulez pas modifier les configs à la main ? Copiez le prompt d'installation et collez-le dans n'importe quel client IA — il effectuera la configuration à sa manière. (Par défaut, il vous guide pour vous connecter et ne vous demande jamais d'envoyer votre API Key dans la conversation.)
detail.access.mcp.composeHint
Tarifs
Facturé une fois par exécution soumise, quel que soit le nombre d'enregistrements renvoyés.
Facturé selon le nombre d'enregistrements renvoyés avec succès. Les exécutions échouées ne sont pas facturées.
Plusieurs événements de facturation se cumulent indépendamment. Voir chaque élément pour les détails. Les exécutions échouées ne sont pas facturées.
Voir les créditsEssayer maintenant
Renseignez les paramètres et lancez l'exécution — les résultats proviennent d'un appel réel.