/marktplaats/listings/search

POST /api/marktplaats/listings/search

Price: 20 credits

Search Marktplaats listings by keyword and/or category: for each result returns title, price, location, seller, images, category attributes and posting date. Supports filters by price range, condition, delivery method, advertiser kind, publication period, postcode radius, construction year and mileage ranges, category-specific attributes and numeric ranges, and sort order. Works across marktplaats.nl, 2dehands.be and 2ememain.be.

How to use it

Search live Marktplaats listings by keyword and/or category_id. Returns listing cards with id, url, listing_title, description, price (EUR), price_type, city/country/latitude/longitude, created_at (unix seconds, day precision), category_id, verticals (taxonomy plus brand tags), attributes, traits, highlights, seller_id/seller_name, is_promoted, is_reserved, has_nap_status and image/images. Filter by min_price/max_price, min_construction_year/max_construction_year, min_mileage/max_mileage, condition, delivery, advertiser (private/business), offered_since, buy_now, urgent, postcode+distance_meters, category-specific attributes (text facets) and attribute_ranges (numeric facets such as engineHorsepower, batteryCapacity, numberOfSeats), plus sort. Use domain to pick the regional site (marktplaats.nl, 2dehands.be, 2ememain.be).

Parameters

• access-token string required

Request body

• timeout 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")
• keyword string nullable — Search keyword (examples: "fiets", "iphone 17"; minLength: 1)
• count integer required — Max number of listings to return (min: 1)
• category_id integer nullable — Top-level category ID to scope the search (examples: 91, 445)
• subcategory_id integer nullable — Subcategory ID to scope the search (examples: 451)
• min_price number nullable — Minimum price in EUR (min: 0)
• max_price number nullable — Maximum price in EUR (min: 0)
• condition array nullable — Filter by item condition (any of the given values) (one of: "Nieuw", "Refurbished", "Zo goed als nieuw", "Gebruikt", "Niet werkend")
• delivery array nullable — Filter by delivery method (any of the given values) (one of: "Ophalen", "Verzenden")
• advertiser string nullable — Filter by advertiser kind (private person or business) (one of: "Particulier", "Bedrijf")
• offered_since string nullable — Only listings published within this period (one of: "Vandaag", "Gisteren", "Een week", "Altijd")
• buy_now boolean — Only listings with instant Buy Now enabled (default: false)
• urgent boolean — Only listings flagged by the seller as must-go (default: false)
• postcode string nullable — Dutch/Belgian postcode used as the centre of a radius search (examples: "1011AB")
• distance_meters integer nullable — Search radius in meters around the postcode (min: 1000)
• min_construction_year integer nullable — Earliest construction year (vehicle categories) (examples: 2020; min: 1900)
• max_construction_year integer nullable — Latest construction year (vehicle categories) (examples: 2024; min: 1900)
• min_mileage integer nullable — Minimum mileage in kilometers (vehicle categories) (min: 0)
• max_mileage integer nullable — Maximum mileage in kilometers (vehicle categories) (examples: 50000; min: 0)
• attributes object nullable — Category-specific filters as facet key/value pairs, e.g. {"fuel": "Benzine", "transmission": "Automaat"}. Available keys depend on the selected category. Numeric facets are not accepted here - use attribute_ranges for those. (examples: {"body":"Stationwagon","fuel":"Benzine"})
  • * string
• attribute_ranges object nullable — Category-specific numeric filters as facet key to "from:to" range, e.g. {"engineHorsepower": "100:200"}. Either bound may be left out ("100:" or ":200"). Available keys depend on the selected category. (examples: {"engineHorsepower":"100:200","numberOfSeats":"5:7"})
  • * string
• sort string — Result ordering (default: "relevance"; one of: "relevance", "date_desc", "date_asc", "price_asc", "price_desc", "construction_year_desc", "construction_year_asc", "mileage_asc", "mileage_desc")

Response

• @type string (default: "MarktplaatsListingCard")
• id string required
• url string nullable
• listing_title string nullable
• description string nullable
• price number nullable
• currency string (default: "EUR")
• price_type string nullable
• city string nullable
• country string nullable
• country_code string nullable
• latitude number nullable
• longitude number nullable
• created_at integer nullable
• category_id integer nullable
• verticals array (default: [])
• attributes object (default: {})
  • * string
• traits array (default: [])
• highlights array (default: [])
• seller_id integer nullable
• seller_name string nullable
• is_verified_seller boolean (default: false)
• is_promoted boolean (default: false)
• is_reserved boolean (default: false)
• has_video boolean (default: false)
• has_nap_status boolean (default: false)
• image string nullable
• images 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 — 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.