Marktplaats Listings Scraper

Export public Marktplaats listing links from keywords or search URLs into an Apify dataset. Enable includeDetails for listing-page titles, descriptions and available prices. Seller identities, locations and category attributes are not populated.

Quick start

1. Open the Actor input and enter one keyword or one public Marktplaats search URL. Clear the other sample field if you do not want both searches.
2. Start with a small limit and enable listing details when you need item-specific information:

{
  "queries": ["bakfiets"],
  "maxItems": 10,
  "includeDetails": true,
  "proxy": { "useApifyProxy": false }
}

3. Run the Actor, then open its dataset and export JSON, CSV or Excel.

Only the supplied search pages are inspected: a larger limit does not fetch subsequent result pages. Without includeDetails, links and IDs identify individual listings, but descriptive fields come from the search page and may repeat across rows. Check availability and field completeness before using results for price comparisons.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

What you get

One saved listing URL with its derived identifier, source search page and collection time. Optional detail requests can supply item-specific titles, descriptions and available prices. Without them, descriptive metadata can repeat from the search page. Seller, location and category attributes remain unpopulated.

Who is it for?

• Second-hand market researchers collecting a bounded set of public listing links.
• Resale analysts checking small detail-enabled samples before comparing visible prices.
• Classifieds researchers retaining source URLs and extraction times for manual review.
• Data teams joining exported listing IDs to their own records or repeated snapshots.

How you can use the data

• Review a small bakfiets sample. Use the existing keyword with a ten-listing cap and details on. Keep listing ID, source link and available listing-specific price and description before manually comparing cargo-bike offers.
• Choose a lighter link export. Use the existing bakfiets search URL with details off when only URLs and IDs are needed. Search-page titles and descriptions can repeat, so do not use that lighter mode as independent item price evidence.
• Combine known searches deliberately. URLs are processed before keywords under one shared cap. Clear the unused sample input when only one source is intended, and keep searchUrl and query to attribute each row.
• Compare your own saved samples. Join listing IDs and collection timestamps in your destination, inspecting the underlying pages for meaningful changes. Sequential rank is output order rather than marketplace rank, and the Actor does not provide built-in change detection or a complete inventory.

Input settings

For a link-focused export without visiting each listing:

{
  "startUrls": [{ "url": "https://www.marktplaats.nl/q/bakfiets/" }],
  "maxItems": 10,
  "includeDetails": false
}

Both examples are input recipes, not public saved tasks.

More input

Provide at least one nonempty queries entry or a startUrls entry. Neither alternative is globally required. When both are supplied, URLs are processed before keywords, with one combined result limit.

Setting	API key	Behavior
Keywords	queries	Search terms, such as bakfiets.
Search URLs	startUrls	Public HTTPS Marktplaats search-page URLs.
Maximum listings	maxItems	Combined saved-row limit. Default 20, form range 1–10000. Not a promised result count.
Listing details	includeDetails	Default false. Enable to read each listing page.
Proxy configuration	proxy	Optional managed Apify Proxy configuration. Direct access by default. See field help for supported settings.

Output data

The dataset contains one row per discovered listing URL. Missing text and prices can be null. rank is the Actor's sequential output position, not a marketplace popularity or price ranking.

Fields	Meaning and limitations
listingId, url	Listing identifier derived from its URL, and the discovered URL.
searchUrl, query, rank	Source page, keyword parsed from a /q/ URL when present, and output position.
title, priceText, priceValue, description, detailDescription	Available page metadata. Listing-specific only when details are enabled. Both description fields contain the same value. Price parsing is best-effort.
priceCurrency, country	Currency when available, otherwise EUR. Country defaults to NL. These defaults are not geographic verification.
imageUrls, reserved	Up to 20 image URL matches and a reserved-text indication from the inspected page. Not a verified listing gallery or availability check.
scrapedAt	Collection timestamp.
priceType, location, city, latitude, longitude, sellerName, sellerId, sellerVerified, categoryId, postedAtText, priorityProduct	Reserved fields currently returned as null.
attributes, extendedAttributes	Currently empty arrays.

Synthetic shape-only example, not a captured listing or a promise of populated fields:

{
  "listingId": "m1234567890",
  "url": "https://www.marktplaats.nl/v/example/m1234567890-example",
  "searchUrl": "https://www.marktplaats.nl/q/bakfiets/",
  "query": "bakfiets",
  "rank": 1,
  "title": null,
  "priceText": null,
  "priceValue": null,
  "priceCurrency": "EUR",
  "description": null,
  "detailDescription": null,
  "sellerName": null,
  "location": null,
  "country": "NL",
  "imageUrls": [],
  "attributes": [],
  "reserved": false,
  "scrapedAt": "2026-10-25T00:00:00.000Z"
}

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is charged once after input validation. The result event applies to each listing accepted for saving. A no-listing run can still incur start, and previously saved results remain chargeable if later work fails. No separate detail-description events or error/status dataset rows apply.

Start with a small row cap, especially when details are enabled. See the Pricing tab for current rates and scheduled changes, including the announced 4 November update.

Tips for best results

• Enable details for item-specific descriptions and prices. Link-only mode can repeat search-page metadata across rows.
• Clear an unwanted sample query or URL. Both sources otherwise contribute under the same cap.
• Keep source search URLs with each listing. They show where the URL was discovered.
• Inspect raw price text before comparing amounts. Price parsing is best-effort and fields can be missing.
• Check final run status before treating no rows as an empty market. Blocking and changed pages can prevent useful extraction.

Limits and caveats

Only public Marktplaats search and listing pages are supported without login or private account data. Seller profiles, contacts, messaging and an exhaustive marketplace feed are outside scope. This is an independent scraper rather than an official Marktplaats API.

Only supplied search pages and generated keyword searches are inspected. A larger saved-row cap does not fetch subsequent result pages. There is no sorting or automatic pagination control, and browser-only URL fragment filters are not guaranteed. Rank is sequential output position, not popularity or price ranking. Repeated listing URLs are saved once within a run.

Details require additional time and can still be incomplete or unavailable. With details off, descriptive fields come from the search page and may repeat. The two description fields contain the same value. Seller, location and category-related fields remain null, with empty attribute arrays in either mode.

Currency and country defaults are not geographic verification. Images are up to twenty matches from the inspected page rather than a verified gallery, and reserved is a text indication rather than a stock or availability check. Prices and other visible metadata can be missing or change.

Blocked pages and request failures can fail a run. A page with no discovered links can produce no rows, but empty output alone does not prove no matching offers exist. Saved results remain available and chargeable if a later request fails. Managed Apify Proxy is optional and does not guarantee access. No complete-description or recovery guarantee is provided.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~marktplaats-listings-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "queries": [
    "bakfiets"
  ],
  "maxItems": 10,
  "includeDetails": true,
  "proxy": {
    "useApifyProxy": false
  }
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/marktplaats-listings-scraper').call({
  "queries": [
    "bakfiets"
  ],
  "maxItems": 10,
  "includeDetails": true,
  "proxy": {
    "useApifyProxy": false
  }
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/marktplaats-listings-scraper').call(run_input={'queries': ['bakfiets'], 'maxItems': 10, 'includeDetails': True, 'proxy': {'useApifyProxy': False}})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API and AI-agent usage notes

The asynchronous REST response contains the run ID and default dataset ID. Wait for SUCCEEDED, then retrieve dataset items. Inspect failure status rather than assuming an empty dataset is a successful search.

MCP and AI agents

You can ask your AI assistant to collect data with Marktplaats Listings Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Marktplaats Listings Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/marktplaats-listings-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Marktplaats Listings Scraper by Fetch Cat, or give it the identifier fetch_cat/marktplaats-listings-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Marktplaats Listings Scraper to collect up to 5 bakfiets listings with details enabled and direct access. Keep listing links, available price text and listing-specific descriptions for my manual comparison.”
• “Collect up to 5 listing links from https://www.marktplaats.nl/q/bakfiets/ with keyword inputs cleared and details off. Keep IDs and source search links, and label descriptive metadata as search-page information.”
• “Retrieve up to 5 bakfiets listings with details enabled and direct access. Keep listing IDs, collection times and raw prices for comparison with my own export, marking missing fields without inferring seller identity or location.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Is this an official Marktplaats API?

No. It is an independent public-page scraper available through Apify's API. It does not provide private accounts, messaging, seller profiles or an exhaustive marketplace feed.

Can I combine keyword searches and URLs?

Yes. URLs are processed first, then keywords. The limit is shared across all inputs, and repeated listing URLs are saved once within a run.

Why do different listings have the same title or description?

With includeDetails: false, descriptive values come from the search page. Enable details for listing-page metadata. Fields can still be missing. Seller and location fields remain empty in either mode.

Can I sort results or fetch more pages?

There is no Actor sorting or automatic pagination control. Supply individual public search-page URLs and inspect the resulting order. rank records output order only. Browser-only URL fragment filters are not guaranteed to apply.

What should I do about blocked pages or empty output?

Try a smaller input and inspect the run status. Managed Apify Proxy is optional, not a guarantee of access. A page with no discovered listing links can produce no rows. Blocking or changed content may also prevent useful extraction.

Related Actors

• eBay Marketplace Scraper — collect public eBay product listings with available prices and item links.
• Vinted Search Scraper — explore second-hand fashion searches.
• Craigslist Classifieds Scraper — collect public Craigslist classified listings with available prices, locations and links.
• Facebook Marketplace Scraper — collect available public Facebook Marketplace listing titles, prices, locations and links.
• Etsy Scraper — research handmade and vintage products.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥