logo
JP

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.

原文 · en-US訳文に戻す

データ収集E-commerce & RetailJD.comProducts
開発者
super_ig
料金
$0.003 / 60 件から
最終更新
2026-10-19

概要

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.

適用範囲と境界

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.

  • 適している用途
  • 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.
  • 適さない用途
  • 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.

失敗時の処理

開発者が宣言した失敗時と再試行の動作です。連携時にはシステムプロンプトに含めることをおすすめします。

  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.

入力

この App の呼び出しに必要なパラメータで、manifest.json の input.schema から生成されています。

  • JD shop IDshop_id必須string
    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.
    例11635291
  • In-shop keywordkeyword必須string
    Enter one keyword to search inside the shop, from 1 to 512 characters.
    例钥匙扣
  • Expected product counttarget_count必須integer
    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.
    範囲1–12000例10
  • Collection sort ordersort_order必須string(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.
    選択可能な値Default0Sales2Review count3Newest4Price: low to high51Price: high to low52例0

出力

1 件のレコードのフィールド構造で、manifest.json の output.schema から生成されています。

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

サンプルデータ

output.schema から生成したサンプルです。サンプル値のないフィールドには構造上のプレースホルダーを使用しています。

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
}

連携方法

この App は MCP、API、SDK、ファイルエクスポートのいずれでも連携でき、どのチャネルも同じ能力と料金を共有します。すべてのリクエストは Authorization: Bearer ヘッダーで認証し、認証情報には API Key（長期有効。Data Hub コンソールで作成）を使用します。MCP クライアントは OAuth によるキー不要のログインにも対応しています。CLI や Skill など、さらに多くの連携方法も準備中です。 この App は非同期で実行され、途中でキャンセルできます：キャンセル後、実行は停止します。納品済みのレコードは保持され、課金対象になります。

MCP（Model Context Protocol）を使うと、Claude や Cursor などの AI クライアントからこの App を直接呼び出せます。クライアントと認証方式を選び、下の設定をコピーしてください。

クライアント設定

Bearer の後の値を長期有効な API Key に置き換えてください。あらゆるクライアント、CI、ヘッドレス環境で利用できます。

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>" }
    }
  }
}
自分の API Keys を表示 →

AI に設定を任せる

設定を手作業で編集したくない場合は、インストールプロンプトをコピーして任意の AI クライアントに貼り付けてください。AI が自分のやり方でセットアップを完了します（プロンプトは AI があなたに API Key を尋ねる形になっているため、認証情報がチャット履歴や共有設定に残りません）。

detail.access.mcp.composeHint

料金

Task submission

返される件数にかかわらず、実行の送信 1 回ごとに課金されます。

$0.001/ 回
Returned 60 record

正常に返されたレコードの件数に応じて課金されます。失敗した実行には課金されません。 60 件を 1 つの課金単位とし、端数は 60 件に切り上げて課金されます。

$0.003/ 60 件

複数の課金イベントはそれぞれ独立して累計されます。詳細は各項目をご覧ください。失敗した実行には課金されません。

Credits を確認

今すぐ試す

パラメータを入力して実行してください。結果は実際の呼び出しによるものです。

サンプル
パラメータは送信前に input.schema で検証されます
$0.003 / 60 件から