/ceneo/shops

POST /api/ceneo/shops

Price: 20 credits

Get one Ceneo shop profile by shop id or shop URL: trading name, registered company name, own website, address, phone, Polish NIP and KRS numbers, number of physical branches, the buyer rating with its wording and review count, the positive/neutral/negative review split over all time, the last year and the last 30 days, Ceneo's order-effectiveness, repeat-purchase and fulfilment-speed metrics, and the awards and trust badges the shop carries.

How to use it

The `shop_id` on every row of /ceneo/products/offers is what this takes, so use it to judge who is behind a cheap offer before treating the price as comparable. `tax_id` (NIP) and `registry_id` (KRS) identify the legal entity in Polish registries. `rating` covers the last 12 months, while `reviews_all_time` counts everything ever left, so a long-running shop can hold a weak recent score against a large history.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• shop string required — Ceneo shop: its numeric shop id or any ceneo.pl shop-profile URL (examples: "25070", "https://www.ceneo.pl/sklepy/empik.com-s25070"; minLength: 1)

Response

• @type string (default: "CeneoShop")
• id string required
• alias string nullable
• name string nullable
• url string nullable
• company_name string nullable
• web_url string nullable
• address string nullable
• phone string nullable
• tax_id string nullable
• registry_id string nullable
• branch_count integer nullable
• rating number nullable
• rating_label string nullable
• rating_count integer nullable
• order_effectiveness_percent number nullable
• would_buy_again_percent number nullable
• fulfilment_speed number nullable
• positive_share_30d_percent number nullable
• reviews_all_time object nullable
  • @type string (default: "CeneoShopReviewCounts")
  • positive_count integer nullable
  • neutral_count integer nullable
  • negative_count integer nullable
• reviews_last_year object nullable
  • @type string (default: "CeneoShopReviewCounts")
  • positive_count integer nullable
  • neutral_count integer nullable
  • negative_count integer nullable
• reviews_last_30_days object nullable
  • @type string (default: "CeneoShopReviewCounts")
  • positive_count integer nullable
  • neutral_count integer nullable
  • negative_count integer nullable
• badges 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 — No Ceneo shop 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.