logo
JP

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.

原文 · en-US訳文に戻す

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

概要

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.

適用範囲と境界

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.

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

失敗時の処理

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

  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.

入力

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

  • JD shop IDshop_id必須string
    The ID of the JD shop whose product listings you want to collect. Enter one shop ID per task, from 1 to 512 characters.
    例1000001140
  • Expected product countcrawl_count必須integer
    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.
    範囲1–1200例25
  • Collection sort ordersort_order必須string(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.
    選択可能な値Default0Sales2Review count3Newest4Price: low to high51Price: high to low52例0

出力

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

  • Collection timecrawl_timestring
    Collection time for the listing; the source does not specify a timezone.
    例2026-10-13T18:41:21
  • Product imageimage_urlstring
    Main product image address from the listing; it may start with //; empty when none is returned.
    例//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.
    例1000001140

サンプルデータ

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

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
}

連携方法

この 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-product-list",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}
自分の API Keys を表示 →

AI に設定を任せる

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

detail.access.mcp.composeHint

料金

Per submitted shop task

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

$0.0001/ 回
Per returned 60 record

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

$0.01/ 60 件

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

Credits を確認

今すぐ試す

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

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