/suning/products

POST /api/suning/products

Price: 10 credits

Get Suning Product

How to use it

Get one Suning product by page URL or by the <shop_code>-<product_id> id that suning/products/search returns: title, selling point, brand, category chain, images, the full specification table, price in CNY, variant ids and review star counts. A product id under a shop code it does not belong to is not found.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Suning product page URL, or <shop_code>-<product_id> as returned in search row ids (examples: "0000000000-12453136079", "https://product.suning.com/0070083734/140372806.html"; minLength: 1)

Response

• @type string (default: "SuningProduct")
• id string required
• product_id string required
• shop_code string required
• url string required
• name string nullable
• selling_point string nullable
• description string nullable
• brand_name string nullable
• brand_id string nullable
• category_code string nullable
• categories array (default: [])
  • @type string (default: "SuningCategory")
  • id string nullable
  • name string nullable
• shop_name string nullable
• image string nullable
• images array (default: [])
• attributes array (default: [])
  • @type string (default: "SuningAttribute")
  • group string nullable
  • name string required
  • value string required
• variant_product_ids array (default: [])
• model_name string nullable
• weight number nullable
• volume number nullable
• flagship_name string nullable
• price number nullable
• list_price number nullable
• currency string nullable
• inventory_status string nullable
• reviews object nullable
  • @type string (default: "SuningReviewSummary")
  • review_count integer nullable
  • five_star_count integer nullable
  • four_star_count integer nullable
  • three_star_count integer nullable
  • two_star_count integer nullable
  • one_star_count integer nullable
  • picture_review_count integer nullable
  • video_review_count integer nullable
  • repeat_review_count integer nullable
  • rating number 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 shop code and product id, or pass the product page 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.