/pult/products

POST /api/pult/products

Price: 20 credits

Get one pult.ru product by its page URL, its slug or its article number: name, brand, the full category path, the current price in RUB with the pre-discount price and the discount in percent and in rubles, the unit the price is quoted per, stock line, rating and review count, barcode, weight and dimensions, the marketing description, the image gallery and the grouped manufacturer specifications.

How to use it

Use this for one known product. A full product URL, the bare slug and the numeric article number printed on the page as 'Артикул' all resolve to the same record. Do not compare prices without reading price_unit: speakers are quoted per pair as often as per item. A minority of products publish no price at all and come back with is_price_shown false and price null — that is the shop quoting on request, not a gap; on the rest, an absent old_price simply means the item is not discounted. Do not guess slugs — search for the product first and pass the url it returns.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Product page URL, its slug, or the numeric article number printed on the page (examples: "naushniki-sennheiser-hd-660s2", "https://www.pult.ru/product/naushniki-sennheiser-hd-660s2", "309810"; minLength: 1)

Response

• @type string (default: "PultProductDetails")
• id string required
• article string nullable
• alias string required
• url string required
• name string nullable
• base_name string nullable
• alternative_name string nullable
• barcode string nullable
• description string nullable
• image string nullable
• images array (default: [])
• brand object nullable
  • @type string (default: "PultBrandRef")
  • id string nullable
  • name string nullable
  • alias string nullable
  • url string nullable
• categories array (default: [])
  • @type string (default: "PultCategoryRef")
  • id string nullable
  • name string nullable
  • url string nullable
• breadcrumbs array (default: [])
• price number nullable
• old_price number nullable
• discount_percent number nullable
• discount_amount number nullable
• currency string (default: "RUB")
• price_unit string nullable
• is_price_shown boolean nullable
• availability string nullable
• is_available boolean nullable
• is_buyable boolean nullable
• is_sale boolean nullable
• is_active boolean nullable
• has_audition_salon boolean nullable
• rating number nullable
• review_count integer nullable
• weight_kg number nullable
• height_mm number nullable
• width_mm number nullable
• length_mm number nullable
• sort_weight integer nullable
• badges array (default: [])
  • @type string (default: "PultBadge")
  • name string required
  • url string nullable
  • image string nullable
• specs array (default: [])
  • @type string (default: "PultSpec")
  • name string required
  • value string required
  • group string nullable
  • spec_type string nullable
  • hint 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 — No such product on pult.ru — the slug or article number resolves to nothing. 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.