/suning/products/search

POST /api/suning/products/search

Price: 20 credits

Search Suning Products

How to use it

Search Suning products by keyword, optionally narrowed to one brand label and ordered by sales, review count or price from high to low. The source repeats products across its result pages, so a narrow keyword can end well below count. Pass a row id to suning/products for specifications and review star counts.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (examples: "手机"; minLength: 1)
• count integer required — Max number of products to return (examples: 120; min: 1; max: 2400)
• sort string — Result order (default: "relevance"; one of: "relevance", "sales", "most_reviewed", "price_high_to_low")
• brand string nullable — Brand name exactly as Suning labels it in the brand filter (examples: "华为(HUAWEI)")

Response

• @type string (default: "SuningSearchProduct")
• id string required
• product_id string required
• shop_code string required
• url string required
• name string nullable
• selling_point string nullable
• image string nullable
• brand_id string nullable
• category_code string nullable
• shop_name string nullable
• shop_url string nullable
• self_operated_label string nullable
• review_count_label string nullable
• variant_product_ids array (default: [])
• price number nullable
• list_price number nullable
• currency string nullable
• inventory_status string nullable
• vendor_name string nullable
• sales_volume string 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 — The entity was not found, or a precondition failed 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.