POST /api/marktplaats/sellers/reviews
Price: 5 credits
Get the reviews left for a Marktplaats seller by seller ID (or profile URL): for each review returns the star score, date, reviewer, the listing it relates to and the praise/improvement tags chosen by the reviewer. Works across marktplaats.nl, 2dehands.be and 2ememain.be.
Fetch reviews for one Marktplaats seller by numeric seller ID or profile URL. Returns reviews with id, score (1-5), created_at (unix seconds), reviewer_id/reviewer_name, is_from_buyer, the related listing (listing_id/listing_title/listing_category), category_scores (per-aspect score breakdown of the deal) and tags (id/text/is_positive). Reviews carry tags and a star score rather than free-text bodies. Dealers whose reputation is hosted externally have no reviews here; their score and a link to it are on the seller endpoint under ratings. Use domain to pick the regional site.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)domain string — Regional Marktplaats site to query (default: "marktplaats.nl"; one of: "marktplaats.nl", "2dehands.be", "2ememain.be")seller string required — Marktplaats seller ID or a seller profile URL containing it (examples: "22472561", "https://www.marktplaats.nl/u/dp-telecom/22472561/"; minLength: 1)count integer required — Max number of reviews to return (min: 1)@type string (default: "MarktplaatsReview")id integer requiredscore integer nullablecreated_at integer nullablereviewer_id integer nullablereviewer_name string nullableis_from_buyer boolean (default: true)listing_id string nullablelisting_title string nullablelisting_category string nullablecategory_scores array (default: [])@type string (default: "MarktplaatsReviewCategoryScore")category string nullablescore integer nullabletags array (default: [])@type string (default: "MarktplaatsReviewTag")id integer nullabletext string nullableis_positive boolean (default: true)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 — Seller not found (well-formed but nonexistent seller 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.