POST /api/pult/categories/products
Price: 20 credits
List the products of one pult.ru category and narrow them by brand, price range, stock and the category's own technical attributes. Returns product cards with the current price in RUB, the pre-discount price, the discount in percent and in rubles, stock and showroom availability, brand, the full category path, rating and review count, article number, barcode, dimensions and weight, and the manufacturer specification pairs.
Bulk price surface: this is the endpoint that walks a whole category. category_id is the numeric id carried by every product's categories list; /pult/categories/filters lists the brand ids, value sets and numeric bounds this category accepts — ids differ per category, so do not reuse them from another one, and an attribute value the category lacks returns no products rather than the unfiltered list. Do not read is_available as 'in stock' here — it is true on a minority of cards; in_stock is the field that narrows to what the shop actually has.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)category_id string required — Numeric category id, as carried by every product's categories list (examples: "2325"; minLength: 1)brand_ids array nullable — Keep only products of these brands, by numeric brand id (examples: ["10332"])price_min number nullable — Lowest accepted price in RUB (min: 0)price_max number nullable — Highest accepted price in RUB (min: 0)in_stock boolean — Keep only products the shop holds in stock (default: false)attributes array nullable — Keep only products matching these category attributesid string required — Attribute filter id from the filters endpoint (examples: "1380378"; minLength: 1)values array required — Keep products whose attribute equals any of these values (examples: ["3"]; minItems: 1)attribute_ranges array nullable — Keep only products whose numeric category attributes fall inside these boundsid string required — Attribute filter id from the filters endpoint (examples: "2018289"; minLength: 1)min number nullable — Lowest accepted value of the attributemax number nullable — Highest accepted value of the attributesort string — Result ordering (default: "popularity"; one of: "popularity", "price", "novelty", "rating")sort_order string — Direction of the chosen ordering (default: "desc"; one of: "asc", "desc")count integer required — Max number of products to return (min: 1)@type string (default: "PultProduct")id string requiredarticle string nullableurl string requiredname string nullablebase_name string nullableoriginal_name string nullablealternative_name string nullablebarcode string nullableimage string nullableimages array (default: [])brand object nullable@type string (default: "PultBrandRef")id string nullablename string nullablealias string nullableurl string nullablecategories array (default: [])@type string (default: "PultCategoryRef")id string nullablename string nullableurl string nullableprice number nullableold_price number nullablediscount_percent number nullablediscount_amount number nullablecurrency string (default: "RUB")is_price_shown boolean nullableis_old_price_hidden boolean nullableis_sale boolean nullableis_available boolean nullableis_buyable boolean nullableis_active boolean nullableis_expected boolean nullableis_similar boolean nullablehas_audition_salon boolean nullablerating number nullablereview_count integer nullableweight_kg number nullableheight_mm number nullablewidth_mm number nullablelength_mm number nullablesort_weight integer nullablebadges array (default: [])@type string (default: "PultBadge")name string requiredurl string nullableimage string nullablespecs array (default: [])@type string (default: "PultSpec")name string requiredvalue string requiredgroup string nullablespec_type string nullablehint string nullable422 — 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 category id on pult.ru. 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.