JD Product Reviews
Collect public JD.com reviews for one product SKU and return the original review payload, publish times, and shop context
Original · en-USVolver a la traducción
super_igDescripción general
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.
Alcance y límites
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.
- Adecuada para
- 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
- No usar para
- 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
Gestión de fallos
Comportamiento de fallos y reintentos declarado por el desarrollador. Recomendamos incluirlo en tu prompt del sistema al integrar.
- 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
Entrada
Parámetros necesarios para llamar a esta App, generados a partir del input.schema del manifest.json.
- JD product SKU
product_skuObligatoriostringThe JD.com product SKU whose public reviews will be collected. Enter one identifier, 1 to 512 characters.Ejemplo100342088268 - Expected review count
comment_countObligatoriointegerThe 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.Rango1–200
Salida
Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.
- Business ID
biz_idstringThe business identifier linking the review record to the collected productEjemplo100342088268 - Comment data
comment_datastringThe original review payload retained as source text, including rating, body text, photos, and buyer nickname when suppliedEjemplo{"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 reviewEjemplo106482610234891880 - Comment time
comment_timestringThe source timestamp of the review without an inferred timezoneEjemplo2026-10-12T12:49:47
Datos de ejemplo
Generado a partir de output.schema. Los campos sin valor de ejemplo usan marcadores de estructura.
{
"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"
}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/jd-comment",
"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. (El prompt le pide a la IA que te solicite tu API Key, de modo que las credenciales nunca queden en el historial de chat ni en configuraciones compartidas.)
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 10 registros; cualquier unidad parcial se redondea a 10 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éditosData Apps relacionadas
Agrega esta App y las recomendaciones de abajo a una colección y genera una configuración MCP lista para conectar a tu cliente de IA.Agrupar estas Apps →
Búsqueda por palabra clave en tienda JD
Indique un ID de tienda JD, una palabra clave en tienda y una cantidad esperada para recopilar productos coincidentes con títulos, precios y contexto de tienda.
super_igDesde 0,003 US$ / 60 registrosLista de productos de tienda JD
Indique un ID de tienda JD y un recuento esperado de productos para recopilar los anuncios de esa tienda, con titulos, precios, senales de ventas e imagenes.
super_igDesde 0,01 US$ / 60 registrosBúsqueda por palabra clave de JD
Indique una palabra clave de búsqueda de JD y una cantidad esperada para obtener listados de productos coincidentes con precios, tiendas y enlaces de producto.
super_igDesde 0,05 US$ / 48 registrosPruébalo ahora
Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.