Marktplaats Scraper: New Listing & Price Alerts

You give this actor a search (a keyword, or a pasted marktplaats.nl search URL) and it returns one row per listing: title, price, price type, city, condition, seller hash, image and link, read straight from Marktplaats' own public /lrp/api/search JSON endpoint. No login, no headless browser, no anti-bot proxy needed for this target. Turn on monitoring and the same search becomes a watch: only listings that are new, or whose price has genuinely dropped, since your last run, charged only for what's delivered and free on a quiet day.

Who it's for

Someone hunting a used iPhone, a road bike or a specific IKEA sofa on Marktplaats who doesn't want to refresh the search page by hand ten times a day. A reseller watching a category for underpriced stock to flip. A developer wiring Marktplaats results into a Discord bot, an n8n workflow or a Google Sheet without maintaining their own scraper against a site that has no official public API. Anyone who has looked at Notifie.nl, MPAlerts.nl or MarktAlert.nl and would rather pay per alert than a monthly subscription for one search.

Why this one

• Reads Marktplaats' own JSON API, not a rendered page. /lrp/api/search is the same endpoint the site's own search page calls client-side. No headless browser, no CAPTCHA, no client-side rendering to wait for.
• Monitoring is built in, not bolted on. Turn on "Only return results that are new or dropped in price" and a search becomes a watchlist: new listings and genuine price drops since your last run, tracked in a named store so it survives between scheduled runs.
• Postcode and distance are real, confirmed filters, not decoration. A postcode + distanceKm pair was tested live against the real API and changes real results, not just the labels on them.
• Never charged for a miss, and never charged for an already-seen listing. A search that turns up nothing costs only the run fee. On a monitored search, a listing you've already been shown once is dropped before billing, not after.
• Seller identity stays off by default. You get a private/business flag and an anonymous seller hash so you can group listings by seller without a name attached; turning on raw seller ID and name is an explicit opt-in.

What you get

Every row starts with the same five fields, then the parent search summary, then one row per listing (turn off "One row per listing" in the Input tab to get one grouped row per search instead of one row per listing; you're charged the same either way).

Field	Type	Description
query	text	The search you submitted, echoed back
found	boolean	true if the search returned at least one listing
status	text	OK on a match; NOT_FOUND, BLOCKED, BAD_FORMAT on a miss
message	text	Plain-English reason for a miss, only present when found is false
scrapedAt	ISO 8601 datetime	When the search was run
searchQuery	text	The keyword actually searched
listingCount	number	Listings returned for this search (what you're billed on)
totalAvailable	number	How many listings Marktplaats reports in total for this search
truncated	boolean	true if more listings existed than were fetched
newCount	number	New listings this run (monitoring only)
priceDropCount	number	Genuine price drops this run (monitoring only)
listingId	text	Marktplaats' own listing ID
url	link	The listing's page on marktplaats.nl
title	text	Listing title
description	text	Listing description, with phone numbers and email addresses replaced by [redacted]
price	number	Price in EUR (Marktplaats' priceCents divided by 100)
priceType	text	FIXED, MIN_BID, FAST_BID, SEE_DESCRIPTION, or Marktplaats' other documented values (BID, FREE, ASKING, TRADE, RESERVED)
city	text	Seller's listed city
countryName	text	Country (almost always Nederland)
postedAt	date	ISO date parsed from Marktplaats' own relative/absolute Dutch text
postedText	text	The original Dutch string ("Vandaag", "Gisteren", "14 sep 26", ...)
imageUrl	link	First listing photo
imageCount	number	How many photos the listing has
condition	text	Condition, when the seller specified one
category	text	Marktplaats' numeric category ID
sellerHash	text	Anonymous hash of the seller ID, always present
sellerVerified	boolean	Marktplaats' own seller-verified flag
sellerType	text	business when the listing carries Marktplaats' Admarkt (dealer console) trait, else private
isPromoted	boolean	true for a paid placement ("Dagtopper" and similar)
sellerId / sellerName	text	Only populated when "Include raw seller ID and name" is on
isNew	boolean	true on a newly-seen listing (monitoring only, else null)
changeType	text	new, price-drop, or seen (monitoring only, else null)
previousPrice	number	The last known price, only on a price-drop row
priceDropPct	number	Percent drop, only on a price-drop row
firstSeenAt	date	When this listing first appeared on a run (monitoring only, else null)

Price

Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed per item only when data is actually found and returned — see .actor/pay_per_event.json for exact prices. A miss is never charged.

1,000 listings through this actor: about $2 at the FREE tier, less on a paid Apify plan, plus a $0.00005 run-start fee. A search that returns nothing costs only that run fee. Compare that to a paid Marktplaats alert subscription (Notifie.nl, MPAlerts.nl, MarktAlert.nl and similar all charge a flat monthly fee regardless of how many alerts you actually get): this only ever charges for listings actually delivered.

How to use

1. In the Apify Console. Open the actor page and click Start — the searches field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~marktplaats-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"searches":["iphone"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

1. Open the Input tab and type one or more searches into "Marktplaats searches to run", one per line, or paste a marktplaats.nl search URL (the filter fragment after # isn't read; use the Postcode, Distance and Price type fields instead).
2. Set "Most listings to return per search" to your budget. Marktplaats' API caps at 100 per request; this actor pages automatically above that, up to 1000.
3. To watch a search instead of running it once, turn on "Only return results that are new or dropped in price" under Monitoring, and optionally name your watchlist.
4. Press Start.

Input

{
  "searches": [
    "iphone"
  ]
}

One search per line — keywords like "iphone", or paste a marktplaats.nl search URL (its filter fragment after # is not read; use the Postcode/Distance/Price type fields below instead). Accepted formats: iphone, racefiets, https://www.marktplaats.nl/q/iphone/.

Sample output

query	found	status	searchQuery	listingCount	totalAvailable	truncated	newCount	priceDropCount	listings	listingId	url	title	description	price	priceType	city	countryName	postedAt	postedText	imageUrl	imageCount	condition	category	sellerHash	sellerVerified	sellerType	isPromoted	sellerId	sellerName	isNew	changeType	previousPrice	priceDropPct	firstSeenAt	scrapedAt
iphone	true	OK							<all listings found (full list)>				<description>	<price (eur)>				<posted (date)>	<posted (as marktplaats words it)>					<seller (anonymous hash)>				<seller id (only with seller info on)>	<seller name (only with seller info on)>	<is this listing new?>		<previous price (eur)>	<price drop %>		1970-01-01T00:00:00.000Z

A search with nothing new comes back as a found: true row with listingCount: 0 and an empty listings array, and is never charged. A search that finds nothing at all comes back as found: false, also never charged.

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~marktplaats-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"searches":["iphone"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~marktplaats-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"searches":["iphone"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~marktplaats-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"searches":["{{search}}"]}, mapping the row's search into the searches array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Marktplaats Scraper | Apify" — the agent will find and run this actor.

Monitoring: only new results

Schedule this actor (Apify Schedule, hourly or daily) with deltaMode: true and a deltaName so the watchlist survives between runs. Each run compares this search's listing IDs against a named key value store (marktplaats-listing-lookup-delta), reports only listings that are genuinely new or whose price has dropped since the last run, and stamps a NO_NEW_ROWS heartbeat, uncharged, on a quiet day. Point the schedule's webhook at Discord, Slack, Google Sheets or n8n to get a live feed instead of a page you refresh by hand.

Turn on "Skip alerts on the first run" if you're seeding a brand-new watchlist and don't want a flood of "new" alerts for listings that were already there before you started watching.

Limitation, stated plainly. A price drop is only visible while the listing is still inside the fetched window (maxListingsPerSearch, and Marktplaats' own newest-first ordering). Widen a search too much and an older listing's price drop can scroll out of range between two runs before either one sees it; keep searches reasonably narrow if price-drop coverage matters to you.

Tips

• Leave "Most listings to return per search" at the default (100) for a single request per search; raising it pages the API automatically, at a proportional cost.
• Set a postcode and distance if you only care about listings near you — both are confirmed, working API filters here, not client-side guesses.
• priceType filtering happens after fetching, so a very narrow price-type filter combined with a low maxListingsPerSearch can return fewer rows than you'd expect; raise the max if so.
• Name your watchlist (deltaName) if you plan to change filters later and want to keep the same monitoring memory across that change; leave it blank and a filter change starts a fresh one automatically.
• A BLOCKED status is unusual on this target (no anti-bot posture was observed), but if you see one, lower "Max concurrency" and try again shortly.

vs. alternatives

	What it costs	What you get	Trade-off
This actor (marktplaats-listing-lookup)	$0.002 per listing returned (FREE tier, less on paid tiers), $0.00005 actor start, nothing for a miss	One row per listing from a Marktplaats search, price, city, condition, seller hash, image, plus optional monitoring for new listings and price drops	No server-side price-range API param was found, so min/max price filtering happens after fetching, not before. A search wider than maxListingsPerSearch can miss an older listing's price drop between two runs.
Notifie.nl / MPAlerts.nl / MarktAlert.nl	Flat monthly subscription (typically a few euros/month per saved search)	A ready-made alert email or app notification, no API needed	If you just want a personal alert and don't need the data anywhere else, one of these is simpler. This is for when you want the data in your own table, workflow, or agent, and would rather pay per row than per month.
Doing it yourself	Your time, plus tracking Marktplaats' JSON field names and handling pagination, redaction and a seen-set for monitoring	The same data	This actor's field mapping, price-drop logic, redaction and delta-store handling are the maintenance burden it absorbs.

Prices for third-party tools are approximate, as researched September 2026, and are not tracked here — check the vendor before relying on the comparison.

FAQ

Why is a row empty, or why does found say false? Either the search returned no listings at all (status: NOT_FOUND), the input wasn't a usable search or URL (status: BAD_FORMAT), or Marktplaats returned an unexpected response (status: BLOCKED). Check the message column. None of these are billed.

Am I charged for a listing I've already seen? No, not with monitoring on. Actor.charge() only fires for listings marked new or a genuine price-drop once delta mode is dropping already-seen rows. Without monitoring, every listing returned is billed once, same as any other run.

Is this a live check or a stored database? Live. Every run calls Marktplaats' own search API fresh; nothing is cached or stored on our side beyond the small watchlist state (listing IDs and last-known prices) that monitoring needs to work, which lives in your own actor's key-value store.

Does postcode + distance actually work? Yes, confirmed live: setting a postcode and a distance changes the returned listings' measured distance and re-centers results, not just a label. There's no confirmed API parameter for a price range, so minPrice/maxPrice are applied after fetching instead.

Is this GDPR-relevant? Seller name, ID and photos can be personal data. sellerHash is on by default so you can group listings by seller without a name; raw sellerId/sellerName are only added when you turn on "Include raw seller ID and name", and doing so makes you responsible for having a lawful basis to process that data. Phone numbers and email addresses embedded in a description are redacted.

Can an AI agent call this directly? Yes. It's registered on the Apify MCP server, an agent in Claude, Cursor, or another MCP client can find and run it by name ("Marktplaats Scraper | Apify"), or call the REST endpoint shown above from any script or workflow tool.

Data & privacy. This actor reads public search results that anyone can see without logging in. It doesn't log in, solve CAPTCHAs or reveal hidden contact details. Seller identity is off by default: you get a private/business flag and an anonymous seller hash so you can group listings by seller without names. Turning on seller info makes you responsible for having a lawful reason to process it. Not affiliated with Marktplaats.

Is this allowed? It collects the same public listing data your browser shows, for the searches you choose. It's built for monitoring a search, not for copying the marketplace. Check that your use fits Marktplaats' terms and your local law.

Related actors

• 2dehands Scraper — the same search, built for Marktplaats' sibling marketplace in Belgium (same underlying API).
• OLX Listing Lookup — the same keyword-search shape, for Poland's largest classifieds marketplace.