logo
ES

JD Shop Product List

Give one JD shop ID and an expected product count to collect that shop's listed products with titles, prices, sales signals, and images.

Original · en-USVolver a la traducción

Recopilación de datosE-commerce & RetailJD.comProducts
Desarrollador
super_ig
Precios
Desde 0,01 US$ / 60 registros
Última actualización
2026-10-16

Descripción general

A JD shop page is a useful window into what a merchant currently offers, but the listings are hard to keep as a comparable dataset: titles, prices, images, and sales signals sit together on the page and shift as the assortment changes. This app turns one shop ID into a structured product-level catalog so merchandising, sourcing, and research teams can review that shop's listed mix without copying rows by hand.

Unlike opening a product you already know, a shop list shows the assortment as it appears in the store itself. Keeping SKU identity, listing commercial signals, and shop context in the same row makes it possible to map price bands, watch which items stay listed, or assemble a candidate set from one merchant.

Data notes

Each record is a public product listing from the supplied JD shop. SKU IDs are de-duplicated within the returned dataset. Source item preserves the shop context and may repeat across many products from the same task. Listings are returned in a stable ascending collection-time order.

JD price and original price are listing amounts as raw strings, with no separate currency field. Sales count and rating count are displayed text, so they should not be treated as audited totals. Collection time has no timezone. Product image addresses may start with // rather than a full http prefix. Some rows still return SKU, shop, and image when title, price, or sales text is empty. A No-data marker distinguishes a shop item that produced no matching products from ordinary listing rows.

The collection covers public listings for the supplied shop only. It does not include other shops, product-detail specifications, comments, or order data.

What a result looks like

Each row is one JD shop product listing associated with the submitted shop, or a no-data marker for that shop.

SKU IDProduct titleShop nameShop IDCollection timeNo-data marker
100300235664绘威耗材京东自营旗舰店10000011402026-10-13T18:41:21No
4154542绘威耗材京东自营旗舰店10000011402026-10-13T18:41:21No

Product image, JD price, original price, brand name, sales count, and rating count are also available when supplied with the record. Product titles and shop names may remain in the original language.

Use cases

  • For assortment mapping, group rows by Shop ID and compare Product title with Shop name to see the shop's visible mix.
  • For catalog monitoring, compare SKU ID and Shop ID across later collections to see which products reappear or drop out of the shop list.
  • For collection review, use Collection time with No-data marker to tell ordinary listing rows from a shop item that produced no matching products.

Alcance y límites

One JD shop ID per task with an expected product count from 1 to 1,200; the count is a collection target, not a hard result cap. Retrieval is protected at 1,000 pages of up to 1,000 records each. Coverage is limited to public JD shop listings.

  • Adecuada para
  • When you need a product-level catalog snapshot for one JD shop.
  • When you want to compare listed titles, displayed prices, and public sales signals within a shop.
  • No usar para
  • When you need product-detail specifications or customer reviews rather than shop-listing data.
  • When you need an immediate single-record lookup rather than a background collection task.

Gestión de fallos

Comportamiento de fallos y reintentos declarado por el desarrollador. Recomendamos incluirlo en tu prompt del sistema al integrar.

  1. 1If no products are returned, check the shop ID and resubmit.
  2. 2Keep completed records after a partial success; resubmit the same shop after a failed or expired task.
  3. 3Retry later after rate limiting, temporary unavailability, or a timeout.
  4. 4Results may exceed the requested target count; the count is a collection target, not a strict output limit.

Entrada

Parámetros necesarios para llamar a esta App, generados a partir del input.schema del manifest.json.

  • JD shop IDshop_idObligatoriostring
    The ID of the JD shop whose product listings you want to collect. Enter one shop ID per task, from 1 to 512 characters.
    Ejemplo1000001140
  • Expected product countcrawl_countObligatoriointeger
    Expected number of products to collect, from 1 to 1,200. This is a collection target, not a hard result cap, so the actual count may be higher.
    Rango1–1200Ejemplo25
  • Collection sort ordersort_orderObligatoriostring(enum)
    Choose how products are collected: Default, Sales, Review count, Newest, Price: low to high, or Price: high to low. Returned rows are still ordered by collection time.
    Valores permitidosDefault0Sales2Review count3Newest4Price: low to high51Price: high to low52Ejemplo0

Salida

Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.

  • Collection timecrawl_timestring
    Collection time for the listing; the source does not specify a timezone.
    Ejemplo2026-10-13T18:41:21
  • Product imageimage_urlstring
    Main product image address from the listing; it may start with //; empty when none is returned.
    Ejemplo//img13.360buyimg.com/n7/jfs/t1/514425/6/8520/200460/6a9e9d91Fc5d50a38/00835dc5dc07cc0e.jpg
  • Product titleproduct_titlestring
    Product title shown on the JD shop listing; empty when none is returned.
  • Shop IDshop_idstring
    Identifier of the shop containing this product.
    Ejemplo1000001140

Datos de ejemplo

Generado a partir de output.schema. Los campos sin valor de ejemplo usan marcadores de estructura.

output.example
{
  "crawl_time": "2026-10-13T18:41:21",
  "image_url": "//img13.360buyimg.com/n7/jfs/t1/514425/6/8520/200460/6a9e9d91Fc5d50a38/00835dc5dc07cc0e.jpg",
  "product_title": "<product_title>",
  "shop_id": "1000001140",
  "shop_name": "绘威耗材京东自营旗舰店",
  "sku_id": "100300235664",
  "source_item": "1000001140",
  "no_data": false
}

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 config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=super_ig/jd-shop-product-list",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}
Ver mis API Keys →

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

Per submitted shop task

Se cobra una vez por cada ejecución enviada, independientemente del número de registros devueltos.

0,0001 US$/ ejecución
Per returned 60 record

Se cobra según el número de registros devueltos correctamente. Las ejecuciones fallidas no se cobran. Se factura en unidades de 60 registros; cualquier unidad parcial se redondea a 60 registros.

0,01 US$/ 60 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éditos

Pruébalo ahora

Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.

Ejemplo
Los parámetros se validan contra input.schema antes del envío
Desde 0,01 US$ / 60 registros