# /proftools/products

`POST /api/proftools/products`

Price: 10 credits

Read one ProfTools (proftools.ru) product by its catalogue URL: name, retail price with and without Russian VAT, the VAT amount, currency, unit of measure, stock state and the quantity the shop will sell, the image gallery, the shop's own short and long description text, the promotional labels it carries and the category it belongs to.

## How to use it

Take url straight from a search or category-products result: proftools.ru gives a product no page of its own under a bare numeric id, so the section chain is the only way in, and a vendor article number reaches a product only through the search endpoint. An ancestor section in the chain resolves too and is normalised back to the canonical URL, so two forms of one product return the same record. price is the retail price the shop publishes, and price_without_vat and vat_amount are its own split of that price at 20% rather than at any current statutory rate, so do not re-derive them. price is null for the small share of items the shop lists without a published price, which is not the same as being unavailable — read is_in_stock for that. The source publishes no old or pre-discount price anywhere, so a promotional label carries no discount with it.

## 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 URL or catalogue path. The trailing numeric id must be preceded by at least one category slug of the chain the product sits in (examples: "https://proftools.ru/catalog/elektroinstrument/dreli/22147/", "elektroinstrument/dreli/22147", "/catalog/ruchnoy_instrument/knipex/32143/"; minLength: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "ProftoolsProduct")
- `id` (string, required)
- `url` (string, required)
- `name` (string, nullable)
- `category` (string, nullable)
- `category_path` (string, nullable)
- `category_url` (string, nullable)
- `price` (number, nullable)
- `price_without_vat` (number, nullable)
- `vat_amount` (number, nullable)
- `currency` (string, nullable)
- `measure` (string, nullable)
- `is_in_stock` (boolean, nullable)
- `stock_status` (string, nullable)
- `available_quantity` (integer, nullable)
- `image` (string, nullable)
- `images` (array) (default: [])
- `summary` (string, nullable)
- `description` (string, nullable)
- `labels` (array) (default: [])

## 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 product is served under this catalogue path.

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.