# /ceneo/products/search `POST /api/ceneo/products/search` Price: 20 credits Search Ceneo products by free-text query, by category, or both, and narrow the result with a price range, the Buy Now and promotional-price switches, and any category-specific attribute the category exposes - multi-choice, colour, numeric range or free text. Each row carries the product id and URL, name, brand, category, image, the cheapest offer price in PLN, how many shops sell it, buyer rating and rating count, the number of colour or capacity variants, the attribute summary Ceneo prints on the card, the free-delivery flag and how many units sold recently. ## How to use it Send a query to find a product by name, a category to walk one section, or both to search inside a section. A query alone lands on whatever category Ceneo resolves it to, so a broad word can silently scope the result - pass category when you know it. The three attribute maps are keyed by the ids /ceneo/categories/filters returns for that same category, and an id in the wrong map is rejected rather than ignored. Rows are products, not offers: `price_min` is the cheapest shop, so use /ceneo/products/offers for the spread, and a price bound matches a product with any offer in range, which is why a cheap-looking card can survive a high `price_min`. ## Parameters - `access-token` (string, required) ## Request body - `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500) - `query` (string, nullable) — Free-text product query (examples: "iphone 16", "ekspres do kawy") - `category` (string, nullable) — Ceneo category to search inside: its URL alias or a full category URL (examples: "Smartfony", "https://www.ceneo.pl/Ekspresy_do_kawy") - `count` (integer, required) — Max number of products to return (min: 1) - `sort` (string) — Result ordering (default: "recommended"; one of: "recommended", "popularity", "price_asc", "price_desc", "rating_desc") - `price_min` (number, nullable) — Keep products with at least one shop offer priced at or above this, in PLN (min: 0) - `price_max` (number, nullable) — Keep products with at least one shop offer priced at or below this, in PLN (min: 0) - `in_stock` (boolean, nullable) — Set true to keep only products buyable through Ceneo's own Buy Now checkout. false behaves the same as leaving the field out - `on_promo` (boolean, nullable) — Set true to keep only products carrying a Ceneo promotional price. false behaves the same as leaving the field out - `attributes` (object, nullable) — Multi-choice and colour attribute filter, as attribute id to a list of value ids. Both id sets come from /ceneo/categories/filters for the same category (examples: {"115200":["1183497","1183889"],"115315":["1305498"]}) - `*` (array) - `attribute_ranges` (object, nullable) — Numeric attribute filter, as attribute id to a two-item [from, to] list of bounds written the way Ceneo writes that attribute's values ('6,1 cala', '4000mAh'). Either bound may be an empty string to leave that side open, and a bound between two of the values /ceneo/categories/filters lists is accepted. A bound Ceneo cannot read as a number is ignored and the result comes back unnarrowed (examples: {"114841":["6,1 cala","7 cali"]}) - `*` (array) - `attribute_text` (object, nullable) — Free-text attribute filter, as attribute id to the phrase to match. Only attributes /ceneo/categories/filters reports as text accept it (examples: {"110154":"Sapkowski"}) - `*` (string) ## Response ### 200 — Successful Response - `@type` (string) (default: "CeneoProductCard") - `id` (string, required) - `url` (string, required) - `name` (string, nullable) - `brand` (string, nullable) - `category` (string, nullable) - `category_id` (string, nullable) - `image` (string, nullable) - `price_min` (number, nullable) - `currency` (string, nullable) - `offer_count` (integer, nullable) - `rating` (number, nullable) - `rating_count` (integer, nullable) - `variant_count` (integer, nullable) - `parameters` (object) (default: {}) - `*` (string) - `recently_purchased_count` (integer, nullable) - `has_free_delivery` (boolean, nullable) - `free_delivery_offer_count` (integer, nullable) - `is_sponsored` (boolean) (default: false) ## 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 The entity was not found, or a precondition failed 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.