/ceneo/products

POST /api/ceneo/products

Price: 20 credits

Get one Ceneo product by numeric id or product URL: name, brand, category path, marketing summary and full description, cheapest and dearest listed offer price in PLN plus the last price Ceneo saw once nobody stocks it any more, number of shops offering it, availability, buyer rating with its star breakdown, per-feature pro/con vote counts, review and question counts, image gallery, the grouped specification sheet, and the other products Ceneo groups into the same model family.

How to use it

Use this for one known product. price_min is the cheapest offer on the page, not a single shop's price - call /ceneo/products/offers for the per-shop spread. When is_in_stock is false no shop offers the product any more: price_min, price_max and offer_count are then null/0 and last_price carries the 'Ostatnia cena' Ceneo still renders. rating_breakdown holds percentages, not counts. Ceneo lists each colour, storage size and pack size as its own product, so a caller comparing 'the same phone' must walk variants; the family block occasionally also holds a matching accessory rather than a variant, which shows up as a price far below the parent.

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", "https://www.ceneo.pl/157123293#tab=reviews"; minLength: 1)

Response

• @type string (default: "CeneoProduct")
• id string required
• url string required
• name string nullable
• brand string nullable
• brand_url string nullable
• category string nullable
• category_id string nullable
• breadcrumbs array (default: [])
  • @type string (default: "CeneoBreadcrumb")
  • id string nullable
  • alias string nullable
  • name string nullable
  • url string nullable
• summary string nullable
• description string nullable
• price_min number nullable
• price_max number nullable
• last_price number nullable
• currency string nullable
• offer_count integer nullable
• is_in_stock boolean nullable
• rating number nullable
• rating_count integer nullable
• rating_breakdown object nullable
  • @type string (default: "CeneoRatingBreakdown")
  • star_5_percent number nullable
  • star_4_percent number nullable
  • star_3_percent number nullable
  • star_2_percent number nullable
  • star_1_percent number nullable
• review_count integer nullable
• question_count integer nullable
• features array (default: [])
  • @type string (default: "CeneoProductFeature")
  • id string nullable
  • name string nullable
  • positive_vote_count integer nullable
  • negative_vote_count integer nullable
• recently_purchased_count integer nullable
• image string nullable
• images array (default: [])
• specifications array (default: [])
  • @type string (default: "CeneoSpecGroup")
  • name string nullable
  • values object (default: {})
    • * string
• variants array (default: [])
  • @type string (default: "CeneoProductVariant")
  • id string required
  • name string nullable
  • url string nullable
  • price_min number nullable
  • image string nullable
• family_id string nullable
• family_name string nullable
• energy_label_url string nullable

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 — No Ceneo product with that id. 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.