/chrono24/dealers/reviews

POST /api/chrono24/dealers/reviews

Price: 1 credit

Get reviews for a Chrono24 dealer by numeric dealer ID. Returns author, country, date, per-category and average ratings, review text, dealer reply, recommendation flag and transaction context.

How to use it

Fetch reviews for a Chrono24 dealer by numeric dealer_id (get it from chrono24/dealers). Returns author name/initials, country, date, average rating plus per-category ratings (article/communication/delivery), review text, dealer reply, recommendation flag, helpful votes and the related transaction (ad title, buyer/seller country, certified status, shipped/delivered dates, info pills, thumbnail). Filter by stars (1-5).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• domain string — Marketplace domain (controls language, currency and regional market). (default: "chrono24.com"; one of: "chrono24.com", "chrono24.co.uk", "chrono24.com.au", "chrono24.ca", "chrono24.in", "chrono24.co.id", "chrono24.my", "chrono24.co.nz", "chrono24.ph", "chrono24.sg", "chrono24.co.za", "chrono24.fi", "chrono24.co.th", "chrono24.ae", "chrono24.de", "chrono24.fr", "chrono24.it", "chrono24.es", "chrono24.nl", "chrono24.at", "chrono24.ch", "chrono24.se", "chrono24.pl", "chrono24.com.br", "chrono24.hk", "chrono24.jp", "chrono24.cn")
• dealer_id integer required — Numeric dealer ID (from chrono24/dealers) (examples: 3144; >: 0)
• count integer required — Max number of reviews to return (min: 1)
• stars integer nullable — Filter by star rating (1-5); omit for all reviews (min: 1; max: 5)

Response

• @type string (default: "Chrono24DealerReview")
• id integer nullable
• author_name string nullable
• author_initials string nullable
• country string nullable
• date string nullable
• rating number nullable
• rating_article integer nullable
• rating_communication integer nullable
• rating_delivery integer nullable
• text string nullable
• dealer_comment string nullable
• recommends_seller boolean nullable
• vote_count integer (default: 0)
• ad object nullable
  • @type string (default: "Chrono24ReviewAd")
  • ad_title string nullable
  • buyer_country string nullable
  • seller_country string nullable
  • certified_status string nullable
  • shipped string nullable
  • delivered string nullable
  • info_pills array (default: [])
  • thumbnail 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 — The entity was not found, or a precondition failed 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.