/dangdang/products

POST /api/dangdang/products

Price: 5 credits

Get Dangdang Product

How to use it

Get one Dangdang product by numeric id or product page URL: title, current and list price in CNY, authors, publisher, ISBN and spec list for books, category breadcrumb, images and review count. Ids come from dangdang/products/search or dangdang/bestsellers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Dangdang product id or product page URL (examples: "29570162", "https://product.dangdang.com/12100024765.html"; minLength: 1)

Response

• @type string (default: "DangdangProduct")
• id string required
• url string required
• name string nullable
• subtitle string nullable
• main_product_id string nullable
• price number nullable
• list_price number nullable
• currency string nullable
• authors array (default: [])
• publisher string nullable
• publish_date string nullable
• isbn string nullable
• attributes array (default: [])
  • @type string (default: "DangdangAttribute")
  • name string required
  • value string required
• category_path string nullable
• category_id string nullable
• categories array (default: [])
  • @type string (default: "DangdangCategory")
  • id string nullable
  • name string nullable
  • url string nullable
• shop_id string nullable
• dd_shop_id string nullable
• supplier_id string nullable
• ebook_id string nullable
• product_type string nullable
• template string nullable
• review_count integer nullable
• image string nullable
• images array (default: [])
• is_sold_out boolean nullable
• is_overseas boolean nullable
• is_virtual boolean nullable
• has_gift_packaging boolean nullable

Errors

• 422 — 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 — Product not found. Check the product id or URL. 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.