POST /api/jd/shops
Price: 1 credit
Get a JD.com (京东) shop by its vendor ID or shop ID. Returns the shop name, description, self-operated flag, fans and goods counts, seller rating scores (overall rank, user evaluation, logistics, after-sale and customer service) with peer grades, logos and banner, hot category names and a preview of top SKUs.
Get a JD.com (京东) marketplace shop by vendor ID or shop ID. Returns id, vender_id, shop_id, name, description, is_self_operated (自营), is_supermarket, fans_count, goods_count, seller DSR ratings (score_rank overall, user_evaluate_score, logistics_score, after_service_score, customer_service_score) and peer grades (comment_grade, logistics_grade, after_service_grade, advice_grade; 高/中/低), image (logo), square_logo, rect_logo, banner, hot_categories and top_skus (id + image). Rating fields are populated for third-party (POP) shops and empty for self-operated (自营) shops.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)shop string required — JD shop vendor ID or shop ID (examples: "1000475228", "1000004123"; minLength: 1)@type string (default: "JdShop")id string requiredvender_id string nullableshop_id string nullablename string requireddescription string nullableis_self_operated boolean (default: false)is_supermarket boolean (default: false)fans_count integer nullablegoods_count integer nullablescore_rank number nullableuser_evaluate_score number nullablelogistics_score number nullableafter_service_score number nullablecustomer_service_score number nullablecomment_grade string nullablelogistics_grade string nullableafter_service_grade string nullableadvice_grade string nullableimage string nullablesquare_logo string nullablerect_logo string nullablebanner string nullablehot_categories array (default: [])top_skus array (default: [])@type string (default: "JdShopSku")id string requiredimage string nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — Shop not found Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.