Marktplaats Scraper — NL Classifieds, Prices, Sellers

Scrape Marktplaats.nl (Netherlands #1 classifieds, ~10M monthly users) by keyword, category, location, price range, and seller type. Returns structured data including price type (fixed/bidding/free), condition, seller info, location, images, and all listing attributes.

What you get

Each record contains:

Field	Description
listing_id	Unique Marktplaats item ID (e.g. m2407274983)
title	Listing title
description	Full description text
url	Direct URL to the listing
price	Price in EUR (float)
price_cents	Price in cents (integer)
price_type	FIXED, MIN_BID, FREE, FAST_BID, or SEE_DESCRIPTION
condition	Item condition (e.g. Zo goed als nieuw, Gebruikt)
location_city	Seller city
location_country	Country abbreviation (NL)
location_lat / location_lng	GPS coordinates
seller_id	Seller ID
seller_name	Seller display name
seller_type	private, business, or null
is_verified	Whether seller is Marktplaats-verified
posted_date	Posting date (raw: Vandaag, Gisteren, or date string)
image_urls	List of full-size image URLs
thumbnail	First image URL
image_count	Number of images
attributes_map	All listing attributes as {key: value} flat dict
is_reserved	Whether listing is reserved
priority_product	Promoted placement type (e.g. DAGTOPPER)
traits	Feature flags list
category_id	Marktplaats category ID

Pricing

Pay per result — charged per listing item returned. $0.90 per 1 000 listings — the lowest credible price in the niche.

Inputs

Input	Description
query	Search keyword(s) — e.g. fiets, iphone 14, volkswagen golf
l1CategoryId	L1 category numeric ID (optional)
l2CategoryId	L2 sub-category numeric ID (optional)
postcode	Dutch postcode for proximity filter (e.g. 1012AB)
distanceMeters	Radius around postcode in meters (e.g. 25000)
priceMin	Minimum price in EUR
priceMax	Maximum price in EUR
sellerType	all (default), private, or business
sortBy	OPTIMIZED (default), SORT_INDEX (by date), PRICE
sortOrder	DECREASING (default) or INCREASING
maxItems	Maximum listings to return (default: 100)
proxyConfiguration	Apify RESIDENTIAL (NL) proxy — recommended

Access

Marktplaats uses a first-party JSON API with no CAPTCHA or JS challenge. Residential NL proxy is recommended for geo-targeting and reliability but is not strictly required for basic use.

Use cases

• Price monitoring — track price history across NL classifieds
• Inventory sourcing — find items by category + location + condition
• Competitive intelligence — monitor seller pricing in a niche
• Lead generation — identify sellers or buyers in specific segments
• Market research — aggregate NL second-hand market data at scale

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Mercadolibre Scraper
• Olx Listings
• Poshmark Listings
• Shopify Products Scraper
• Tiktok Shop Scraper
• Uber Eats Menu Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.