2dehands & 2ememain Scraper — GDPR-safe listings data

Extract listings from 2dehands.be and 2ememain.be — Belgium's largest second-hand marketplaces — as clean, structured JSON. Prices, descriptions, categories, locations, images and posting dates, ready for price monitoring, market research and data pipelines.

No seller personal data, ever. This scraper is built GDPR-first: seller names, IDs, phone numbers and profile links never appear in the output — not as an option you have to remember to switch off, but by design. The only seller information included is whether the listing comes from a business or a private seller.

Quick start (30 seconds)

1. Put what you'd type in the 2dehands search box into searchQuery — e.g. gazelle.
2. Click Start. That's the whole minimum setup.
3. When the run finishes, open the dataset's Overview tab for a clean table, or Export it as CSV/Excel/JSON.

Everything else — price range, category, sorting, the French-language 2ememain.be variant — is an optional refinement, explained in the Input table below. To make it run by itself, create a Schedule in the Apify Console with the same input and add an email or Slack integration on the runs.

What you can build with it

• Flip underpriced finds before anyone else. Sort by date, watch a category like road bikes or PS5 consoles, and get every new listing the minute it posts — with the price and condition already parsed, so your alert fires while the deal is still live.
• Price a car properly. Pull every BMW 5-Series within a year range and read mileage, constructionYear, fuel, transmission and the options list straight from attributes — build the price-vs-mileage curve that tells you what a car is really worth.
• Track a market week over week. Snapshot "e-bikes in Antwerp under €800" on a schedule and watch supply, median price and how fast things sell move over time — the raw material for a pricing report or a dashboard.
• Feed an AI agent clean data. Every field is structured, predictable and free of personal data, so an assistant or pipeline can consume it directly — no scrubbing, no compliance review before you store it.

What you get

Each listing is one dataset item:

{
  "listingId": "m2419606891",
  "title": "Jongensfiets Gazelle Esprit zwart",
  "description": "Nieuw aangekocht in oktober 2024...",
  "priceCents": 40000,
  "priceType": "MIN_BID",
  "city": "Balen",
  "country": "België",
  "latitude": 51.166343,
  "longitude": 5.189532,
  "postedAt": "Vandaag",
  "imageUrls": ["//images.2dehands.com/api/v1/..."],
  "categoryId": 455,
  "url": "https://www.2dehands.be/v/fietsen-en-brommers/...",
  "attributes": { "condition": "Zo goed als nieuw", "frameHeight": "57 cm", "color": "Zwart" },
  "reserved": false,
  "sellerType": "private"
}

Category-specific attributes come through automatically. A car carries constructionYear, mileage, fuel, transmission, body and its full options list; a house carries livingArea and numberOfRooms; a phone carries storage and cameraResolution — whatever the marketplace records for that category, minus anything that identifies a seller.

Field notes, so you know exactly what you are buying:

• priceCents is the asking price in euro cents; listings without a price omit it. priceType tells you how to read it: FIXED (asking price) or MIN_BID (minimum bid), plus the marketplace's other kinds when they occur.
• postedAt is the posting date exactly as the marketplace displays it — a date, or a relative label like Vandaag (today) for recent listings.
• latitude/longitude are the marketplace's own municipality-level coordinates, not a seller address.
• description is the snippet the marketplace search returns, not the full listing page text.
• imageUrls are protocol-relative (//images...); prepend https: to use them.
• attributes is the whitelisted, non-personal spec set for the listing's category — condition and delivery on anything, plus e.g. car specs, property size or phone storage where they apply. Multi-value fields like a car's options come through as a list.
• reserved tells you whether the marketplace currently marks the listing as reserved.

How much does it cost to scrape 2dehands?

$1.99 per 1,000 listings delivered, pay-as-you-go — no subscription, no charge for empty or failed runs. In plain dollars:

• 100 listings ≈ $0.20 — a daily category watch.
• 500 listings ≈ $1.00 — a solid market snapshot.
• A 5,000-listing crawl ≈ $10 — a full category, deduplicated.

The per-result price is all-inclusive — no separate platform-usage charges, no residential proxy surcharge. Higher Apify plans get automatic unit-price discounts (down to $1.59/1,000 on Gold).

Free-plan runs are limited to a sample of 25 items, enough to evaluate the output format against your real query.

Not technical? Let your AI assistant set it up

Copy this into ChatGPT, Claude or any AI assistant, fill in the one line, and follow the conversation:

Help me set up the "2dehands & 2ememain Scraper" actor on Apify
(https://apify.com/lowlanddata/tweedehands-scraper). Guide me one step at a time.

What I want to watch: [E.G. "electric bikes under 800 EUR, alert me on new listings"]

Guide me to:
1. Propose my input values: searchQuery (what I'd type in the site's search box),
   optional priceMinEur/priceMaxEur, optional postcode + radiusKm for
   listings near me (Belgian postcode, e.g. 2000 for Antwerpen), optional
   conditions (new/as-new/used/refurbished/not-working) and delivery
   (pickup/shipping), sortBy "date" for newest-first monitoring, and maxItems.
   To re-check specific listings I already know, use listingIds instead.
2. If my watch fits one category: run one broad search first, read the categoryId
   from the results I care about, and add it to the input for precise runs.
3. Create a free Apify account (apify.com), open the actor page, paste the values
   into the Input form, and start a run.
4. Set up a daily Schedule in the Apify Console with the same input, plus an email
   or Slack integration so new results reach me automatically.
5. Show me how to export results as CSV/Excel, or read them from the API if I code.

Input

Field	Description
searchQuery	Free-text search, e.g. gazelle. Provide this, a category, or both.
domain	2dehands.be (Dutch, default) or 2ememain.be (French). Same listings, different language.
categoryId	Numeric category ID to scope the crawl. See below for finding IDs.
listingIds	Fetch these exact listings instead of searching, e.g. ["m2107483664"] (the id in every listing URL and dataset item). Great for re-checking price or availability.
postcode / radiusKm	Radius search: Belgian postcode (e.g. 2000) plus a radius in km. Results include the distance in meters.
conditions	Only these conditions: new, as-new, used, refurbished, not-working.
delivery	pickup, shipping, or any (default).
buyItNowOnly	Only listings with the "Direct Kopen" option.
priceMinEur / priceMaxEur	Only listings within this price range, in EUR.
sortBy	date (newest first, default), price_asc, price_desc, or relevance.
maxItems	Stop after this many listings. Default 1,000.

A run needs at least a search query or a category — the marketplace has no "everything" feed, and the actor tells you so up front instead of returning an empty dataset.

Finding a category ID

Every result includes its categoryId. The quickest way to discover IDs is to run a broad search once and read the category IDs off the results you care about, then use them as input for scoped crawls.

Use it from your code

Run the actor and get items straight back with one HTTP call (fine for scoped runs up to ~5 minutes):

curl "https://api.apify.com/v2/acts/lowlanddata~tweedehands-scraper/run-sync-get-dataset-items?token=<YOUR_API_TOKEN>" \
  -X POST -H "Content-Type: application/json" \
  -d '{"searchQuery": "gazelle", "maxItems": 100}'

Node.js:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_API_TOKEN>' });
const run = await client.actor('lowlanddata/tweedehands-scraper').call({
  searchQuery: 'gazelle',
  maxItems: 100,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Python:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_API_TOKEN>")
run = client.actor("lowlanddata/tweedehands-scraper").call(
    run_input={"searchQuery": "gazelle", "maxItems": 100})
items = client.dataset(run["defaultDatasetId"]).list_items().items

For large split crawls, start the run asynchronously and fetch the dataset when the finished-run webhook fires. Schedules (e.g. a daily price snapshot), webhooks and the Make/Zapier/n8n integrations all work out of the box — this is a standard Apify actor.

Use it with AI agents (MCP)

Claude, Cursor and other MCP-capable agents can run this scraper as a tool through Apify's hosted MCP server: the agent fills in the search itself, starts the run and reads the results — no glue code.

Claude Code:

$claude mcp add apify --transport http "https://mcp.apify.com?actors=lowlanddata/tweedehands-scraper"

Cursor or Claude Desktop (add a custom connector / MCP server with this URL):

https://mcp.apify.com?actors=lowlanddata/tweedehands-scraper

Sign in with your Apify account when prompted — runs are billed to it. Setup details per client: Apify MCP docs, or start from this actor's own MCP page: apify.com/lowlanddata/tweedehands-scraper/api/mcp.

Prompts that work once connected:

• "Find the 20 newest Gazelle e-bike listings under €800 on 2dehands and put them in a table by price."
• "Snapshot road bikes in the €500–1500 range and tell me the median asking price."
• "Check 2ememain for PS5 consoles posted today and flag anything at least 20% under the median."

Beyond the 5,000-result window

The marketplace API returns at most 5,000 results per query. This scraper automatically splits large queries by category and price band and deduplicates across the shards, so broad crawls are not silently truncated at 5,000 items — a common limitation of similar scrapers. A 60,000-result crawl has been verified end-to-end.

Is it legal to scrape 2dehands?

Public listing data — prices, descriptions, categories, locations — is public commercial information, and this scraper is built so that the hard part of the question never arises: no personal data enters your dataset in the first place. That is the difference between this actor and a generic scraper, where GDPR compliance is your problem to solve after the fact.

Seller-identifying fields are removed structurally before anything reaches your dataset — the mapper whitelists fields in, it does not filter fields out, so new marketplace fields can never leak through. The only seller signal kept is business vs private. Requests are rate-limited to keep load on the marketplace negligible, and no anti-bot protections are bypassed.

One honest limit: titles and descriptions are the seller's own words, delivered as-is. If a seller chooses to type contact details into their listing text, that text is not rewritten — the guarantee covers the marketplace's data fields, not the content sellers publish about themselves.

Troubleshooting

The actor fails fast with the reason in the run's status message:

• "Provide a search query, a category, or both." — the input was empty; fill in searchQuery and/or categoryId.
• "priceMinEur must not be higher than priceMaxEur." — inverted price range.
• Unknown category errors — the marketplace rejected the categoryId; re-check it against a recent result.
• Fewer items than requested on a free plan — the 25-item free sample cap; run on a paid Apify plan for full results.

Is there a 2dehands API alternative?

2dehands and 2ememain publish no public API. This actor is the practical alternative: the same listings as structured JSON through one HTTP call (run-sync-get-dataset-items), on a schedule, or as an MCP tool for AI agents — with the GDPR question already answered in the data itself.

Does 2dehands block scrapers?

The marketplace serves search results openly, and this actor stays inside that welcome: paced requests, standard datacenter proxies, load kept negligible. No CAPTCHA fights, no bot-wall cat-and-mouse — which is also why runs are fast and reliable enough for daily schedules.

How do I monitor 2dehands prices?

Set sortBy: "date" with your query, cap maxItems to a page or two, and add a daily (or hourly) Schedule in the Apify Console with an email/Slack integration on the runs — every new listing lands in your inbox with the price already parsed. The AI-assistant prompt above walks a non-technical user through exactly this setup.

FAQ

Can I get seller names or phone numbers? No — by design. That is the product: data you can store, share and process without a GDPR review. The output tells you only whether the seller is a business or a private person.

What is the difference between 2dehands.be and 2ememain.be? The same marketplace in Dutch and French. Pick the domain whose language you want listings in; the data shape is identical.

How fresh is the data? Live at run time — every run queries the marketplace directly. For continuous freshness, schedule the actor.

Can I export to Excel or CSV? Yes — every dataset exports as CSV, Excel, JSON or XML from the Apify Console or API.

What happens above 5,000 results? The marketplace API caps any single query at 5,000; the actor automatically splits by category and price band and deduplicates, so large crawls come through complete.

Do I get full listing descriptions? You get the description snippet the marketplace search returns, not the full listing page text — stated honestly here rather than discovered later.

Does it work with Make, Zapier or n8n? Yes — it is a standard Apify actor; all platform integrations, webhooks and schedules apply.

Related scrapers

Working the Benelux/German second-hand market? The same GDPR-clean guarantee, same output shape:

• Marktplaats.nl Scraper — the Netherlands' largest marketplace.
• Kleinanzeigen.de Scraper — Germany's largest classifieds site, with full descriptions and spec tables.

Support

Found an issue or missing a field you need? Open an issue on the actor's Issues tab — reports get fixed, this actor is actively maintained.