# /pult/categories/products

`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.

## How to use it

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.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (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 attributes
  - `id` (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 bounds
  - `id` (string, required) — Attribute filter id from the filters endpoint (examples: "2018289"; minLength: 1)
  - `min` (number, nullable) — Lowest accepted value of the attribute
  - `max` (number, nullable) — Highest accepted value of the attribute
- `sort` (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)

## Response

### 200 — Successful Response

- `@type` (string) (default: "PultProduct")
- `id` (string, required)
- `article` (string, nullable)
- `url` (string, required)
- `name` (string, nullable)
- `base_name` (string, nullable)
- `original_name` (string, nullable)
- `alternative_name` (string, nullable)
- `barcode` (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)
- `price` (number, nullable)
- `old_price` (number, nullable)
- `discount_percent` (number, nullable)
- `discount_amount` (number, nullable)
- `currency` (string) (default: "RUB")
- `is_price_shown` (boolean, nullable)
- `is_old_price_hidden` (boolean, nullable)
- `is_sale` (boolean, nullable)
- `is_available` (boolean, nullable)
- `is_buyable` (boolean, nullable)
- `is_active` (boolean, nullable)
- `is_expected` (boolean, nullable)
- `is_similar` (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 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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.

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.