/proftools/products/search

POST /api/proftools/products/search

Price: 20 credits

Search the ProfTools (proftools.ru) catalogue by text and return product cards with the catalogue URL, title, retail price in roubles and its unit of measure, stock state, the quantity the shop will sell, the promotional labels the card carries, the category path and the thumbnail.

How to use it

Search proftools.ru, a Russian Bosch/Dremel/Knipex/Wera dealer. A vendor article number resolves the exact item, and that is the only way to reach a product from an article code. Feed a result's url straight into the product endpoint. price is null for items the shop lists without a published price, which is not the same as being unavailable.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Text matched against the product's title and its detail description, including the manufacturer article number (examples: "дрель", "0601217100", "knipex"; minLength: 1)
• count integer required — Max number of products to return (min: 1)
• sort string — Result ordering (default: "default"; one of: "default", "price_asc", "price_desc", "id_asc", "id_desc")

Response

• @type string (default: "ProftoolsProductCard")
• id string required
• url string required
• name string nullable
• category_path string nullable
• image string nullable
• price number nullable
• currency string nullable
• price_measure string nullable
• is_in_stock boolean nullable
• stock_status string nullable
• available_quantity integer nullable
• labels array (default: [])

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 — Proftools did not return a search results page for this query. 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.