JD Product Reviews
Collect public JD.com reviews for one product SKU and return the original review payload, publish times, and shop context
Source · en-USRevenir à la traduction
Aperçu
Public JD.com product reviews capture how buyers describe quality, delivery, and the SKU they actually purchased. This Data App turns the public review area of one JD product SKU into a consistent set of records covering the original review payload, publish times, shop context, and collection timestamps.
The result is built for repeatable reputation analysis instead of scrolling a product page. Each review keeps its source wording inside Comment data and stays linked to the Source SKU, SKU ID, and shop, so praise and complaints can be compared across collection runs with the same fields.
Data notes
The data covers publicly visible JD.com product reviews for the supplied JD product SKU at collection time, taking the newest public reviews. Returned records keep the order of Collected at from earliest to latest. Each normal record is identified by its Comment ID, which removes duplicate reviews in the same run. Private, deleted, and non-public reviews are outside the coverage.
Comment data keeps the original review payload as source text, including buyer nicknames, ratings, photos, videos, and body text when the source supplies them that way. Comment type, Parent ID, Shop type, and SKU ID are source codes, not rewritten labels. Comment time, Published at, and Collected at preserve the source timestamps without inferring a timezone. Source SKU and No data retain the collection outcome when a product has no public review result.
What the results look like
Each normal record represents one publicly visible review of the selected JD product.
| Comment ID | Business ID | Comment type | Published at | Collected at | Shop name |
|---|---|---|---|---|---|
| 106482610234891880 | 100342088268 | 1 | 2026-10-12T12:49:47 | 2026-10-13T18:37:16 | 小米京东自营旗舰店 |
| 106184670214532716 | 100342088268 | 1 | 2026-10-12T12:17:42 | 2026-10-13T18:37:16 | 小米京东自营旗舰店 |
Additional values include Comment data, Shop type, SKU ID, and No data.
Use cases
- Read Comment data to locate quality complaints, then group by Comment type.
- Compare Published at with Collected at to see how recently the review was captured.
- Split records by Shop name and Shop type when comparing self-operated and marketplace listings.
- Use No data with Source SKU to distinguish an empty listing from a failed collection.
Périmètre et limites
Each run accepts one JD product SKU and an expected review count of 1 to 2000. Results are returned in complete batches and may round up. Only publicly visible JD reviews are covered. Pull protection capacity is 150 pages / 3,000 records.
- Adapté pour
- When you need public JD.com review payloads, publish times, and shop context for one product SKU
- When you need original review text plus collection timestamps for JD reputation analysis
- À ne pas utiliser pour
- When you need reviews from a marketplace other than JD.com
- When you need real-time monitoring of newly posted reviews instead of one collection snapshot
- When you need private, deleted, or otherwise non-public reviews
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 no reviews are returned, verify the JD product SKU and use No data to distinguish an empty listing from a failed job
- 2A partial success still returns the reviews that were completed; submit a new collection after failure or expiry
- 3If authentication fails, a task context does not match, or the job times out, check the credential in the execution environment and submit a new collection instead of reusing the old job
- 4When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
Entrée
Paramètres requis pour appeler cette App, générés à partir de l'input.schema du manifest.json.
- JD product SKU
product_skuRequisstringThe JD.com product SKU whose public reviews will be collected. Enter one identifier, 1 to 512 characters.Exemple100342088268 - Expected review count
comment_countRequisintegerThe expected number of public reviews to collect, from 1 to 2000. Results are returned in complete batches, so the actual count may round up. If the product has fewer public reviews, the result may still be lower.Plage1–200
Sortie
Structure des champs d'un enregistrement, générée à partir de l'output.schema du manifest.json.
- Business ID
biz_idstringThe business identifier linking the review record to the collected productExemple100342088268 - Comment data
comment_datastringThe original review payload retained as source text, including rating, body text, photos, and buyer nickname when suppliedExemple{"afterUserComment": {}, "avatar": "storage.360buyimg.com/i.imageUpload/6a645f3562616533316234626665623831373638333636333633333131_sma.jpg", "content": "好用好看", "creationTime": "2026-10-12 12:49:47", "guid": "T6NYPc91jp0tdhmCU6-ZyHeB", "id": "106482610234891880", "images": [{"imgUrl": "//img30.360buyimg.com/shaidan/s128x96_jfs/t1/536818/26/12014/1878056/6acc66eaF385886de/00a98dcfc0d5070d.jpg"}], "likeCount": "0", "nickname": "eatt94", "plusAvailable": "0", "productColor": "脂白", "productSize": "", "referenceName": "小米(MI)REDMI Buds 8 真无线蓝牙耳机主动降噪适用于安卓苹果手机 脂白", "score": "5", "videos": null} - Comment ID
comment_idstringThe stable unique identifier of the JD reviewExemple106482610234891880 - Comment time
comment_timestringThe source timestamp of the review without an inferred timezoneExemple2026-10-12T12:49:47
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": "100342088268",
"comment_data": "{\"afterUserComment\": {}, \"avatar\": \"storage.360buyimg.com/i.imageUpload/6a645f3562616533316234626665623831373638333636333633333131_sma.jpg\", \"content\": \"好用好看\", \"creationTime\": \"2026-10-12 12:49:47\", \"guid\": \"T6NYPc91jp0tdhmCU6-ZyHeB\", \"id\": \"106482610234891880\", \"images\": [{\"imgUrl\": \"//img30.360buyimg.com/shaidan/s128x96_jfs/t1/536818/26/12014/1878056/6acc66eaF385886de/00a98dcfc0d5070d.jpg\"}], \"likeCount\": \"0\", \"nickname\": \"eatt94\", \"plusAvailable\": \"0\", \"productColor\": \"脂白\", \"productSize\": \"\", \"referenceName\": \"小米(MI)REDMI Buds 8 真无线蓝牙耳机主动降噪适用于安卓苹果手机 脂白\", \"score\": \"5\", \"videos\": null}",
"comment_id": "106482610234891880",
"comment_time": "2026-10-12T12:49:47",
"comment_type": "1",
"crawl_time": "2026-10-13T18:37:16",
"customer": "yunfan",
"no_data": false,
"origin_comment_id": "106482610234891880",
"pid": "0",
"publish_time": "2026-10-12T12:49:47",
"shop_id": "1000004123",
"shop_name": "小米京东自营旗舰店",
"shop_type": "京东自营店",
"sku_id": "100342088268",
"source_sku": "100342088268"
}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/jd-comment",
"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. (Le prompt demande à l'IA de vous réclamer votre API Key, afin que les identifiants ne finissent jamais dans l'historique de conversation ni dans des configs partagées.)
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. Facturé par unités de 10 enregistrements ; toute unité incomplète est arrondie à 10 enregistrements.
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.