logo
ES

JD Keyword Search

Give a JD search keyword and an expected count to get matching product listings with prices, shops, and product links.

Original · en-USVolver a la traducción

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

Descripción general

Keyword searches on JD mix official stores, authorized sellers and accessory listings behind the same buying intent. Seeing those search-result cards together makes it easier to judge which products, shops and price points actually appear for a query, without opening every listing one by one.

This collection keeps the original product titles, displayed prices and listing links from JD search results. It is useful when assortment, ranking and list-page pricing are the input to a sourcing or competitive review, rather than replacing a product-detail check or a purchase decision.

Data notes

The data describes product cards collected from public JD keyword search results. Results are delivered in ascending collection-time order, which is separate from the sorting used to select products during collection. Repeated SKU IDs are consolidated across the delivered pages.

Product title, Price, Review count and Sales count retain their source text. Price is not converted into another currency, and no assumptions are made about taxes, promotions or purchasing conditions. Business ID, Keyword and Submitted keyword can carry the same search phrase; none of them is a unique product identifier. The time zone of Collection time is not specified.

Missing brand, sales-count and listing-status values remain missing rather than being inferred. A blank preview does not assert that the corresponding source value is an empty string. Search-desc flag is kept as a yes/no marker as collected. The collection should not be treated as a complete JD catalog, a stock snapshot, or a verified offer for a particular order.

What the results look like

Each row represents one JD search-result listing. Quoted Price and Review count values are text, not converted numbers.

SKU IDProduct titlePriceReview countShop name
10235644935262苹果18promax【新品限售】Apple iphone18promax 18promax 手机apple 18Promax 6.9英寸 勃艮第酒红色 256GB【全新未激活+全国联保】"12888.00""2000+"星盟3C数码买手店
10234915484680Apple/苹果 iPhone 18 Pro Max 支持移动联通电信 5G 双卡双待手机 勃艮第酒红色 256GB 授权正品【需现场签收激活】 官方标配"10999.00""500+"Apple产品萌宠主题旗舰店

Additional columns include Product URL, Image URL and Collection time.

Use cases

  • Compare search assortment: group Product title by recurring product or accessory terms, then use SKU ID and Shop name to separate distinct listings behind the same keyword.
  • Review displayed pricing: compare Price and Review count for listings with similar Product title wording, keeping the original text before drawing conclusions about competitiveness.
  • Prepare a shortlist: combine Keyword, Product title, Product URL and Shop name to identify relevant candidates, and retain Collection time so later reviews can distinguish collection snapshots.

Alcance y límites

One JD search keyword per task with an expected result count from 1 to 2000; results are collected in source pages and may return fewer or more than requested; fetch protection is 110 pages / 2,200 records; reaching this capacity does not establish completeness; coverage is limited to public JD search listings.

  • Adecuada para
  • When you need JD search-result products for a brand, product, or category keyword.
  • When you need a structured list that connects each matched listing with its shop, price, and product link.
  • No usar para
  • When you need a full product page, variants, reviews, or price history — this App only returns search-result listing information.
  • When you need a strictly capped result count or an immediate single-record lookup.

Gestión de fallos

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

  1. 1If submission times out or its outcome is unknown, check the existing run before submitting again: repeated submissions can create separate jobs.
  2. 2If no matching records are returned, try a shorter or broader search phrase and resubmit.
  3. 3Keep completed records after a partial success; resubmit the same input after a failed or expired task.
  4. 4Retry later after rate limiting, temporary service unavailability, or a timeout.
  5. 5If authentication fails, verify the API Key configured for the execution environment.

Entrada

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

  • Search keywordkeywordObligatoriostring
    Enter one JD product search keyword, from 1 to 512 characters.
    Ejemploiphone 18 pro max
  • Expected product counttarget_countObligatoriostring
    Enter a whole number from 1 to 2000 as digits only. This is a collection target, not a strict cap; source-page collection can return fewer or more listings.
    Ejemplo25
  • Collection sort ordersortObligatoriostring(enum)
    Choose how products are ordered during collection. Default is the JD default ranking. Delivered results remain in ascending collection-time order.
    Valores permitidosDefault0Comprehensive1Sales2Review count3Newest4Price: low to high51Price: high to low52Predeterminado0Ejemplo0

Salida

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

  • SKU IDskuIdstring
    JD product identifier used to distinguish listings.
    Ejemplo10235644935262
  • Business IDbizIdstring
    Search keyword retained on the listing; not a unique product identifier.
    Ejemploiphone 18 pro max
  • Product titleproductTitlestring
    Product title as collected, without translation.
    Ejemplo苹果18promax【新品限售】Apple iphone18promax 18promax 手机apple 18Promax 6.9英寸 勃艮第酒红色 256GB【全新未激活+全国联保】
  • Pricepricestring
    Price text as collected; no currency or numeric conversion is applied.
    Ejemplo12888.00

Datos de ejemplo

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

output.example
{
  "skuId": "10235644935262",
  "bizId": "iphone 18 pro max",
  "productTitle": "苹果18promax【新品限售】Apple iphone18promax 18promax 手机apple 18Promax 6.9英寸 勃艮第酒红色 256GB【全新未激活+全国联保】",
  "price": "12888.00",
  "saleCount": "<saleCount>",
  "rateCount": "2000+",
  "brandName": "<brandName>",
  "imageUrl": "https://img11.360buyimg.com/img/jfs/t1/514884/11/15012/128777/6aacf40fF7127ae8f/00833203200b14b8.png",
  "productUrl": "https://item.jd.com/10235644935262.html",
  "shopId": "13365898",
  "shopName": "星盟3C数码买手店",
  "keyword": "iphone 18 pro max",
  "searchDescFlag": false,
  "status": "<status>",
  "crawlTime": "2026-10-13T18:37:40",
  "taskItem": "iphone 18 pro max",
  "taskNoData": 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-keyword-search",
      "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

Task submission

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

0,0001 US$/ ejecución
Returned record

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

0,05 US$/ 48 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,05 US$ / 48 registros