JD.com Shop API

Read the product rows of one JD.com shop by shop_id: item_id, title, price, currency, image_url and available, with the shop's shop_id, shop_name and shop_url on each row, billed in tiers by the number of rows returned, $0.02881 per tier.

JD.com Shop lists the products of one JD store, given its shop_id. Each row carries the product's item_id, title, link, price and currency, main image and the store's name, ID and page link. It shows what a store sells and at what prices, so brands can audit authorized resellers, sellers can study a competitor's range, and analysts can follow a store's assortment and pricing over time.

shop_id is the numeric store ID, or the store page link https://mall.jd.com/index-<number>.html minus any query string or fragment; a product ID will not do. Every item_id is a numeric JD product ID that the other JD capabilities take without conversion. price comes without a currency symbol, so read it with currency, and keep shop_name and shop_url with the rows to label stores in reports.

  • limit has a maximum of 60; page with page or page_token.
  • item_id goes straight to product_detail, product_price and skus.
  • Failed calls and empty results are not charged.

API health

24h health
Normal
  • Healthy / normal
  • Available
  • Limited
  • Mostly down
Normal

Last 24 hours

Last 30 days

  1. 1Request

    POST /api/v1/social
    {
      "platform": "jd",
      "action": "shop",
      "params": {
        "shop_id": "1000004259"
      }
    }
  2. 2JSON response

    {
      "results": [
        {
          "item_id": "100386940168",
          "title": "HUAWEIWATCH GT7Pro碳晶黑46mm钛合金&纳米微晶陶瓷户外进阶运动21天超长续航华为智能手表",
          "price": 2688,
          "currency": "CNY"
        },
        …
      ],
      "count": 24
    }
  3. 3Rows

    item_idtitlepricecurrency
    100386940168HUAWEIWATCH GT7Pro碳晶黑46mm钛合金&纳米微晶陶瓷户外进阶运动21天超长续航华为智能手表2688CNY
    100343412080华为MateBook 14 鸿蒙版笔记本电脑 国家补贴 2.8K OLED触控屏 鸿蒙AI 24GB 1TB原野绿 圆键盘7599CNY
  4. 4CSV

    jd-shop-sample.csv item_id,url,title,price,currency,shop_id,shop_name,shop_url,image_url,available,platform

A request with shop_id goes in, and one page of that shop's products comes back; each row in results is one product, listed as a field table and a CSV file.

What data you get

The table shows a real call for 1000004259, captured November 7, 2026 at 14:47 (UTC), that returned 24 rows. Your own calls return these fields as listed in the field reference.

item_idurltitlepricecurrencyshop_idshop_nameshop_urlimage_urlavailableplatform
100386940168https://item.jd.com/100386940168.htmlHUAWEIWATCH GT7Pro碳晶黑46mm钛合金&纳米微晶陶瓷户外进阶运动21天超长续航华为智能手表2688CNY1000004259华为京东自营旗舰店https://mall.jd.com/index-1000004259.htmlhttps://img14.360buyimg.com/n0/jfs/t1/550965/17/7947/140219/6ae2b424F7cc9d94c/00835a05a09af40b.jpgnulljd
100343412080https://item.jd.com/100343412080.html华为MateBook 14 鸿蒙版笔记本电脑 国家补贴 2.8K OLED触控屏 鸿蒙AI 24GB 1TB原野绿 圆键盘7599CNY1000004259华为京东自营旗舰店https://mall.jd.com/index-1000004259.htmlhttps://img14.360buyimg.com/n0/jfs/t1/537470/34/12588/89809/6acef399F2a2483a1/00835a05a01f9084.jpgnulljd

Use cases

  • Watch a competitor's pricing

    Read the same shop on a schedule and compare price by item_id.

  • Build a shop catalog

    Store item_id, title and image_url as a list to use as the base table for product research.

  • Audit authorized resellers

    A brand reads each reseller's product rows to see whether title and price match what was agreed.

  • See a shop's price band

    Use the price values of the rows you read to see how the shop's prices spread.

Limits and gotchas

  • shop_id is required: a numeric JD shop ID, or https://mall.jd.com/index-<number>.html with no query string or fragment. It is not a product ID.
  • Set the page size with limit, up to 60. Each page is billed in tiers by the rows it returns, tiers for rows not returned are refunded, and an empty page is not charged.
  • You can page two ways: start at page 1 and pass next_page_token back unchanged as page_token, or jump to page N with page. When both are present, page_token wins.
  • The products you can read have a fixed depth limit. The last page has no next_page_token and pagination.stop_reason is depth_limit, so the number of rows returned is not the shop's product total.
  • From page 2, products come from a saved list that is at most one hour old. When you jump with page, pages can share or miss a product, so de-duplicate by item_id.
  • available is null when the page gives no status; read the reason a single product is out of stock with product_price.

Pricing

Billing is in tiers by the number of products the page returns: each tier counts as one call at $0.02881. Tiers for rows not returned are refunded, and an empty page is not charged. A jump to page N with page is billed as the full pages before it plus page N, the same as paging there one page at a time. Failed calls and empty results are not charged.

CallsCost
10,000$288.06
100,000$2,880.56
1,000,000$28,805.56

Totals use the list price per call.

Code samples

#
bash
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "jd",
  "action": "shop",
  "params": {
    "shop_id": "1000004259"
  }
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

API reference

See the parameters, response fields, errors and billing for shop, and copy the page or open it as Markdown for an AI assistant.

POST

AI prompt

#
Please help me write a data collection script with the EveryInfra JD.com Shop endpoint (jd/shop).

How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to jd and action to shop, and put the parameters inside params.
- Required parameters:
  - shop_id: Identifies the shop used by the shop action. Pass a digit string or the canonical legacy URL https://mall.jd.com/index-<digits>.html without a query or fragment.
- Optional parameters:
  - page: Page number of the shop's products, an integer; leave it out or send 1 for the first page. It runs from 1 to 168 ÷ limit, rounded up: 1–7 at the default limit 24, 1–3 at limit 60.
  - page_token: Page token. Leave it out for the first page. When the response has a next_page_token, pass it back as page_token, exactly as received, to get the next page, with the other parameters unchanged.
  - limit: The most rows to return in this call, an integer from 1 to 60. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 24)
- Returns a list of records. Main fields of each record: item_id (JD numeric product ID), url, title, price, currency, shop_id (JD numeric shop ID), shop_name (Public shop name), shop_url (Public JD shop page), image_url (Image URL: in search, product_detail, s…), available (Whether the item could be bought when i…).
- Example request body:
{
  "platform": "jd",
  "action": "shop",
  "params": {
    "shop_id": "1000004259"
  }
}
- Price: $28.81 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

#
NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYesjdPlatform identifier, fixed value.
actionbodystringYesshopCapability identifier, fixed value.
shop_idbody.paramsstringYes-Identifies the shop used by the shop action. Pass a digit string or the canonical legacy URL https://mall.jd.com/index-<digits>.html without a query or fragment; cross-host URLs are rejected, and this selector does not accept a product item_id.
pagebody.paramsintegerNo-Page number of the shop's products, an integer; leave it out or send 1 for the first page. It runs from 1 to 168 ÷ limit, rounded up: 1–7 at the default limit 24, 1–3 at limit 60. With page, the page size is the limit of this request (1–60). Every page is billed at the price of page 1, tiered by the rows on that page alone, one call per 24 rows: at limit 24 a page is 1 call; at limit 60 a page of 60 rows is 3 calls, and the last page (rows 121–168, 48 rows) is 2 calls. Asking for page N directly bills N pages, the same as paging from page 1 to page N (the N − 1 pages before it as full pages, plus page N itself): limit 24 with page 5 is 5 calls, and limit 60 with page 3 is 3 + 3 + 2 = 8 calls. Blocks for rows of page N that did not come back are refunded, and nothing is charged for the request if page N is empty (for example, the list is not that long). A page that is out of range, 0, negative, fractional, a string such as "2" or a boolean is rejected with 422 before charging. A sync call reaches the deepest page, row 168; you do not need "mode": "async". The deepest page (page 7 at limit 24) has no next_page_token and pagination.stop_reason is depth_limit; a list that is simply shorter ends with end_of_list. Page 1 is fetched fresh on every request. From page 2 on, rows are cut in order from one saved full list (up to 168 rows), and when you first ask for page 2 or later that list is at most one hour old. A page requested with page is cut from that list by its original position (page N is the limit rows starting at row (N − 1) × limit + 1); it does not know what the page 1 you got earlier looked like, so between a separately fetched page 1 and it, or between pages requested across an hour boundary, a few products can repeat or be missing: dedupe by item_id when merging. To read the whole list with no repeats, start at page 1 and follow next_page_token. pagination.page is the page number of this page, and pagination.has_more true means there is a next page: ask for page + 1, or pass next_page_token back as page_token. When both page and page_token are sent, page_token wins. A page requested with page also returns a next_page_token; the next call can use it with or without page.
page_tokenbody.paramsstringNo-Page token. Leave it out for the first page. When the response has a next_page_token, pass it back as page_token, exactly as received, to get the next page, with the other parameters unchanged. Every page keeps the page size of the limit of the request that returned the token, and a later limit has no effect. You can also skip the token and ask for a page number with page; when both are sent, page_token wins. A token is valid for 24 hours and works only for the same shop and the same account; a token used with another shop is rejected with 422 and not charged. Every page is billed at the price of page 1, tiered by the rows on that page alone, one call per 24 rows: at limit 24 each page is 1 call, so paging to page 5 is 5 calls; at limit 60 a page of 60 rows is 3 calls, and the last page (rows 121–168, 48 rows) is 2 calls. Blocks for rows that did not come back are refunded, and an empty page (for example, past the end of a short list) is not charged. Paging stops at row 168 (7 pages at limit 24), and a sync call gets there: you do not need "mode": "async". The page that holds row 168 has no next_page_token and pagination.stop_reason is depth_limit; a list that is simply shorter ends with end_of_list. Page 1 is fetched fresh on every request. From page 2 on, rows are cut in order from one saved full list (up to 168 rows), and when you first ask for page 2 or later that list is at most one hour old. When you page from page 1 with page_token, every later page is cut from that same list: products already given on page 1 do not come back and nothing is skipped in between, so there are no repeats between pages. Slow paging makes no difference: the token chain keeps using the list it had when it first reached page 2. pagination.page is the page number of this page, and pagination.has_more true means there is a next page: pass next_page_token back as page_token. A page requested with page also returns a next_page_token; the next call can use it with or without page.
limitbody.paramsinteger (1–60)No24The most rows to return in this call, an integer from 1 to 60. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

Response example

#
Captured November 7, 2026 at 14:47 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.
json
{  "id": "req_…",  "platform": "jd",  "action": "shop",  "results": [    {      "item_id": "100386940168",      "url": "https://item.jd.com/100386940168.html",      "title": "HUAWEIWATCH GT7Pro碳晶黑46mm钛合金&纳米微晶陶瓷户外进阶运动21天超长续航华为智能手表",      "price": 2688,      "currency": "CNY",      "shop_id": "1000004259",      "shop_name": "华为京东自营旗舰店",      "shop_url": "https://mall.jd.com/index-1000004259.html",      "image_url": "https://img14.360buyimg.com/n0/jfs/t1/550965/17/7947/140219/6ae2b424F7cc9d94c/00835a05a09af40b.jpg",      "platform": "jd"    },    {      "item_id": "100343412080",      "url": "https://item.jd.com/100343412080.html",      "title": "华为MateBook 14 鸿蒙版笔记本电脑 国家补贴 2.8K OLED触控屏 鸿蒙AI 24GB 1TB原野绿 圆键盘",      "price": 7599,      "currency": "CNY",      "shop_id": "1000004259",      "shop_name": "华为京东自营旗舰店",      "shop_url": "https://mall.jd.com/index-1000004259.html",      "image_url": "https://img14.360buyimg.com/n0/jfs/t1/537470/34/12588/89809/6acef399F2a2483a1/00835a05a01f9084.jpg",      "platform": "jd"    }  ],  "next_page_token": …,  "pagination": { … },  "count": 24,  "billing": {    "charged": …,    "charged_usd": …,    "balance_after_usd": …,    …  },  "quota": { … }}

Response fields

#

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

FieldMeaning
item_idJD numeric product ID. From search results you can pass it straight to detail, reviews, or price calls.
urlLink to the record on the platform.
titleTitle. null when the platform has no titles (for example text-only posts).
pricePrice as a number without a currency symbol; see currency.
currencyCurrency code of the price (for example CNY, USD). If price is present but currency is null, do not assume a currency.
shop_idJD numeric shop ID.
shop_namePublic shop name.
shop_urlPublic JD shop page.
image_urlImage URL: in search, product_detail, shop and skus it is the product's main (cover) image; in description_images it is the description image of that row (the full-size https image on JD's image host).
availableWhether the item could be bought when it was read (product_detail, product_price and shop rows); false when out of stock, null when the page did not say.
platformSource platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

Errors and billing

#
401
Missing or invalid key.
402
Insufficient balance. Top up first.
422
Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429
Per-minute request limit reached. Wait for Retry-After, then try again.
503
Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty
No data. No charge.

Errors

Official references

#

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

  • JD.com JSSDK: Separate SKU and Shop Targets ↗

    JD.com's redirect documentation uses `skuId` for a product-detail target and `shopId` for a shop-detail target. This supports keeping product and shop identifiers separate; it does not establish webpage collection rights, supported URL parsing, complete shop catalogs, or EveryInfra request behavior.

    Checked 2026-09-11

FAQ

Where do I find a JD shop ID?

On the store's own page: in https://mall.jd.com/index-<number>.html, the number is the shop ID, and you can pass either the number or that link without a query string. Results from JD Search and Product details also carry a shop_id for the store selling each product.

Can I start from a product link?

Not directly, since shop_id takes a store ID and a product ID is not a valid value. Read the product with JD Product details first; the shop_id in that result names the store, and you can pass it here to list the rest of the store's range.

How do I check prices and availability for the listed products?

The rows carry price and currency as the store lists them. For the current price and whether a product can be bought right now, pass its item_id to JD Product price; for variants, stock state and the full product record, use JD Product details. Buyer feedback comes from JD Reviews.

Which fields does the JD shop API return?

Each row is one product: item_id, url, title, price, currency, image_url and available, with the shop's shop_id, shop_name and shop_url.

How is one page of shop products billed?

By the rows the page returns, in tiers: each tier is one call at $0.02881, or $28.81 per 1,000 calls. Failed calls and empty results are not charged.

You can call the other JD.com endpoints with the same EveryInfra API key.

Google Analytics needs consent. Privacy