/wildberries/products

POST /api/wildberries/products

Price: 1 credit

Get full Wildberries product details by article (nmId) or product URL: name, brand, price, rating, reviews count, seller, colors, sizes with stock, photos, characteristics and description.

How to use it

Fetch a single Wildberries product by article (nmId, e.g. 1212302347) or a product URL. Returns one item with id, url, imt_id, name, alias, brand, subject_name, vendor_code, description, supplier_name/supplier_id/supplier_rating, rating, review_rating, feedback_count, price/list_price, total_quantity, colors, sizes (name+price+quantity), image+images, characteristics (spec name/value). Use the region field to price for a specific delivery region.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• region string — Delivery region — drives price, stock and availability. (default: "moscow"; one of: "moscow", "spb", "krasnodar", "novosibirsk", "khabarovsk", "kazan", "rostov", "belarus", "kazakhstan", "kyrgyzstan")
• product string required — Wildberries product article (nmId) or a product URL containing it (examples: "1212302347", "https://www.wildberries.ru/catalog/1212302347/detail.aspx"; minLength: 1)

Response

• @type string (default: "WildberriesProductDetail")
• id integer required
• url string required
• imt_id integer nullable
• name string required
• alias string nullable
• brand string nullable
• brand_id integer nullable
• subject_id integer nullable
• subject_parent_id integer nullable
• subject_name string nullable
• subject_root_name string nullable
• vendor_code string nullable
• description string nullable
• supplier_name string nullable
• supplier_id integer nullable
• supplier_rating number nullable
• rating number nullable
• review_rating number nullable
• feedback_count integer (default: 0)
• photo_count integer (default: 0)
• is_new boolean (default: false)
• price number nullable
• list_price number nullable
• total_quantity integer (default: 0)
• colors array (default: [])
  • @type string (default: "WildberriesColor")
  • id integer required
  • name string required
• sizes array (default: [])
  • @type string (default: "WildberriesSize")
  • name string nullable
  • orig_name string nullable
  • option_id integer nullable
  • price number nullable
  • list_price number nullable
  • quantity integer (default: 0)
• promotions array (default: [])
• image string nullable
• images array (default: [])
• characteristics array (default: [])
  • @type string (default: "WildberriesCharacteristic")
  • name string required
  • value string required

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 (valid-looking article but no such product) 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.