# /ceneo/products/offers `POST /api/ceneo/products/offers` Price: 20 credits List every shop offer Ceneo holds for one product: shop name, shop id, Ceneo shop page and shop logo, the shop's buyer rating and rating count, the listing name and price the shop gives it in PLN, delivery cost and free-delivery flag, declared dispatch time, the shop's promotional label, Ceneo's click-tracked link to the offer, and whether the row is a paid placement or supports Ceneo's own Buy Now checkout. ## How to use it This is the price-spread endpoint: one row per shop selling the product. Ceneo shows a shortlist on the product page and hides the rest, so use this rather than reading prices off /ceneo/products, which only gives the cheapest and dearest. `price` excludes delivery — add `delivery_cost`, which is 0 when `has_free_delivery` and null when the shop states no figure. `is_sponsored` marks a paid placement, not a dearer one - the cheapest offer is sometimes itself sponsored, so never drop those rows to find the best price. It can only be true on the default sort: Ceneo removes the paid block from an explicitly sorted view, so sorting by total_price_asc for delivery costs you the flag. A product no shop currently offers answers 200 with an empty list. Each colour and capacity is a separate Ceneo product, so offers for one id cover one exact variant. `url` is Ceneo's own click-tracking redirect and commonly does not resolve to the shop page - use `shop_url` to reach the shop itself. ## Parameters - `access-token` (string, required) ## Request body - `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500) - `product` (string, required) — Ceneo product: a numeric product id or any ceneo.pl product URL (examples: "157123293", "https://www.ceneo.pl/157123293"; minLength: 1) - `count` (integer, required) — Max number of offers to return (min: 1) - `sort` (string) — Order the shop offers are listed in (default: "best"; one of: "best", "price_asc", "price_desc", "total_price_asc", "total_price_desc", "shipping_fastest", "shop_rating_desc", "shop_rating_asc") ## Response ### 200 — Successful Response - `@type` (string) (default: "CeneoOffer") - `id` (string, required) - `product_id` (string, required) - `url` (string, nullable) - `name` (string, nullable) - `price` (number, nullable) - `currency` (string, nullable) - `delivery_cost` (number, nullable) - `has_free_delivery` (boolean, nullable) - `delivery_text` (string, nullable) - `shipping_text` (string, nullable) - `promo_label` (string, nullable) - `image` (string, nullable) - `position` (integer, nullable) - `offer_type` (string, nullable) - `is_sponsored` (boolean) (default: false) - `has_buy_now` (boolean) (default: false) - `has_trusted_reviews` (boolean) (default: false) - `is_reliable_seller` (boolean) (default: false) - `shop_id` (string, nullable) - `shop_name` (string, nullable) - `shop_url` (string, nullable) - `shop_logo` (string, nullable) - `shop_rating` (number, nullable) - `shop_rating_count` (integer, nullable) - `shop_offer_count` (integer, 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 Ceneo product with that id. 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.