/ceneo/products/qa

POST /api/ceneo/products/qa

Price: 20 credits

List the buyer questions asked about one Ceneo product, each with its answers: who asked, the optional subject line and the question text, when it was posted, its usefulness votes, how many answers exist in total, and for every answer the author, whether the author is the shop's official account, the text and the post time.

How to use it

Answers written by shops are marked `is_shop` and are the ones that state delivery, invoice and warranty terms. `answer_count` is what Ceneo reports for the question while `answers` holds only the ones the page renders, so the two differ on busy questions - read `answer_count` for volume, `answers` for content.

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 questions to return (min: 1)

Response

• @type string (default: "CeneoQuestion")
• id string required
• product_id string required
• url string nullable
• author string nullable
• subject string nullable
• text string nullable
• created_at integer nullable
• helpful_vote_count integer nullable
• unhelpful_vote_count integer nullable
• answer_count integer nullable
• answers array (default: [])
  • @type string (default: "CeneoAnswer")
  • id string required
  • author string nullable
  • is_shop boolean (default: false)
  • text string nullable
  • created_at integer 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.