logo
ES

JD Shop Keyword Search

Give one JD shop ID, an in-shop keyword, and an expected count to collect matching products with titles, prices, and shop context.

Original · en-USVolver a la traducción

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

Descripción general

In-shop keyword search on JD shows how one merchant presents products for a buying intent. Official items, accessories, and related SKUs sit together on that shop's search page, so the same query can look very different from site-wide results. Seeing those cards in one table makes it easier to judge which titles, price points, and SKUs the shop actually surfaces, without opening listings one by one.

This collection keeps original product titles, displayed JD and original prices, images, and shop context from public in-shop search results. It is useful when a merchant's keyword assortment and list-page pricing are the input to 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 in-shop keyword search for one shop and one keyword. 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, JD price, Original price, Review count and Sales count retain their source text. Prices are not converted into another currency, and no assumptions are made about taxes, promotions, or purchasing conditions. Business ID and Keyword can carry the same search phrase; neither is a unique product identifier. Submitted item keeps the shop and keyword context and may repeat across many products from the same task. The time zone of Collection time is not specified. Product image addresses may start with // rather than a full http prefix.

Missing brand, price, 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. No-data indicator distinguishes a submitted shop-and-keyword item that produced no matching products from ordinary listing rows. The collection should not be treated as a complete shop catalog, a stock snapshot, or a verified offer for a particular order.

What the results look like

Each row represents one in-shop JD search-result listing for the submitted shop and keyword.

SKU IDProduct titleShop nameKeywordCollection time
10106482729387ZEEHO极核插画车型主题高透亚克力钥匙扣 ae8ZEEHO官方旗舰店钥匙扣2026-10-14T17:02:03
100007662145ZEEHO极核钥匙扣挂件ZEEHO官方旗舰店钥匙扣2026-10-14T17:02:03

Additional columns include JD price, Original price, Image URL, and No-data indicator.

Use cases

  • Compare in-shop 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 JD price and Original price for listings with similar Product title wording, keeping the original text before drawing conclusions about competitiveness.
  • Prepare a shortlist: combine Keyword, Product title, Image 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 shop ID and one in-shop keyword per task, with an expected product count from 1 to 12,000. The count is a collection target, not a hard result cap, so fewer or more listings may be returned. Fetch protection is 12 pages / 12,000 records; reaching this capacity does not establish completeness. Coverage is limited to public JD in-shop search listings.

  • Adecuada para
  • When you need products that match a keyword inside one JD shop rather than site-wide search results.
  • When you want a structured list that connects each matched listing with its title, displayed prices, and shop context.
  • No usar para
  • When you need a full product page, variants, reviews, or the complete shop catalog without a keyword filter.
  • 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, check the shop ID and try a shorter or broader in-shop keyword, then 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.

  • JD shop IDshop_idObligatoriostring
    Enter the ID of the JD shop whose in-shop search results you want to collect. Use one shop ID per task, from 1 to 512 characters.
    Ejemplo11635291
  • In-shop keywordkeywordObligatoriostring
    Enter one keyword to search inside the shop, from 1 to 512 characters.
    Ejemplo钥匙扣
  • Expected product counttarget_countObligatoriointeger
    Enter a whole number from 1 to 12,000. This is a collection target, not a hard result cap; the actual count follows what is collected and may be lower or higher.
    Rango1–12000Ejemplo10
  • Collection sort ordersort_orderObligatoriostring(enum)
    Choose how products are selected during collection: Default, Sales, Review count, Newest, Price: low to high, or Price: high to low. Delivered rows remain in ascending collection-time order.
    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.

  • SKU IDskuIdstring
    JD product identifier used to distinguish listings.
    Ejemplo10106482729387
  • Business IDbizIdstring
    Search keyword retained on the listing; not a unique product identifier.
    Ejemplo钥匙扣
  • Product titleproductTitlestring
    Product title as collected, without translation.
    EjemploZEEHO极核插画车型主题高透亚克力钥匙扣 ae8
  • JD pricejdPricestring
    JD listing price as collected text; missing values are not filled in. No separate currency field is provided.

Datos de ejemplo

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

output.example
{
  "skuId": "10106482729387",
  "bizId": "钥匙扣",
  "productTitle": "ZEEHO极核插画车型主题高透亚克力钥匙扣 ae8",
  "jdPrice": "<jdPrice>",
  "originalPrice": "<originalPrice>",
  "saleCount": "<saleCount>",
  "rateCount": "<rateCount>",
  "brandName": "<brandName>",
  "imageUrl": "//img12.360buyimg.com/n7/jfs/t1/224484/24/20441/30093/666a9032Fee15908b/1ef4fa11ad6ec0fc.jpg",
  "shopId": "11635291",
  "shopName": "ZEEHO官方旗舰店",
  "keyword": "钥匙扣",
  "status": "<status>",
  "crawlTime": "2026-10-14T17:02:03",
  "taskItem": "{\"keywords\":\"钥匙扣\",\"shop_id\":\"11635291\"}",
  "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-shop-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,001 US$/ ejecución
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,003 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,003 US$ / 60 registros