2dehands Scraper: Belgium New Listing Alerts

You give this actor a search (a keyword, or a pasted 2dehands.be / 2ememain.be search URL) and it returns one row per listing: title, price, price type, city, condition, seller hash, image and link, read straight from the same public /lrp/api/search JSON endpoint that powers marktplaats.nl in the Netherlands. No login, no headless browser, no anti-bot proxy needed. Turn on monitoring and the same search becomes a watch: only listings that are new, whose price has genuinely dropped, or (opt-in) that have disappeared since your last run, charged only for what's delivered and free on a quiet day. A 2dehands sold items tracker: turn on "Alert on removed listings" and this doubles as a sell-through rate monitor for a category or a search of your own.

Who it's for

Someone in Belgium hunting a used iPhone, a bike or a specific item on 2dehands who doesn't want to refresh the search page by hand. A reseller watching a category for underpriced stock. A developer wiring 2dehands results into a Discord bot, an n8n workflow or a Google Sheet without maintaining their own scraper. French speakers get the same data through the same actor via the "Site" setting (2ememain.be), rather than needing a second tool.

Why this one

• Reliability first. The Store's current 2dehands leader (fatihtahta, 41 users) has a measured 16% timeout rate. This actor calls the platform's own JSON API directly, with no browser render step and no scraping of a rendered page to time out on — every live run in this build's verification came back in single-digit seconds.
• Reads 2dehands' own JSON API, not a rendered page. /lrp/api/search is the same endpoint the site's own search page calls client-side. No CAPTCHA, no client-side rendering to wait for.
• Covers both language front ends from one actor. 2dehands.be (Dutch) and 2ememain.be (French) are the same marketplace, same listings, same sellers, confirmed live by comparing the identical listing ID across both sites' responses — pick one with the "Site" input, or paste either site's URL directly.
• 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. A postcode + distanceKm pair was tested live against the real API (central Brussels, 15km) and changes real results.
• 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; 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 the site 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)
goneCount	number	Listings detected gone this run (monitoring only; counted even with "Alert on removed listings" off)
sellThroughRate	number	Lifetime gone / tracked for this watchlist, 0-1 (monitoring only)
medianPrice	number	Median EUR price across everything this run fetched (monitoring only)
listingId	text	The platform's own listing ID (shared across 2dehands.be and 2ememain.be)
url	link	The listing's page on whichever site you searched
title	text	Listing title
description	text	Listing description, with phone numbers and email addresses replaced by [redacted]
price	number	Price in EUR
priceType	text	FIXED, MIN_BID, FAST_BID, SEE_DESCRIPTION, or the platform's other documented values (BID, FREE, ASKING, TRADE, RESERVED)
city	text	Seller's listed city
countryName	text	Country (almost always België / Belgique)
postedAt	date	ISO date parsed from the site's own relative/absolute date text
postedText	text	The original 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	Numeric category ID
sellerHash	text	Anonymous hash of the seller ID, always present, shared across both sites
sellerVerified	boolean	The platform's own seller-verified flag
sellerType	text	business when the listing carries the Admarkt (dealer console) trait, else private
isPromoted	boolean	true for a paid placement
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, gone, 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)
lastSeenAt	date	The last run this listing was actually seen on (monitoring only, else null)
daysListed	number	Days between first and last sighting (monitoring only, else null)
lastPrice	number	The price it last had, only on a gone row
gonePresumedSold	boolean	Only on a gone row — see "Sold signal and sell-through" below

Price

• Listing returned: $2 per 1,000 listings

Plus a $0.00005 start fee per run. Each event above is billed independently, only when it actually returns data — misses (found:false) are 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.

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~2dehands-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 "2dehands / 2ememain searches to run", one per line, or paste a 2dehands.be / 2ememain.be search URL (the filter fragment after # isn't read; use the Postcode, Distance and Price type fields instead).
2. Pick "Site": 2dehands.be (Dutch) or 2ememain.be (French). A pasted URL's own site always wins over this setting.
3. Set "Most listings to return per search" to your budget. The API caps at 100 per request; this actor pages automatically above that, up to 1000.
4. 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.
5. Press Start.

Input

{
  "searches": [
    "iphone"
  ]
}

One search per line — keywords like "iphone", or paste a 2dehands.be or 2ememain.be search URL (its filter fragment after # is not read; use the Postcode/Distance/Price type fields below instead). A pasted URL's own site wins over the "Site" setting. Accepted formats: iphone, fiets, https://www.2dehands.be/q/iphone/, https://www.2ememain.be/q/iphone/.

Sample output

query	found	status	searchQuery	listingCount	totalAvailable	truncated	newCount	priceDropCount	goneCount	sellThroughRate	medianPrice	listings	listingId	url	title	description	price	priceType	currency	city	countryName	postedAt	postedText	imageUrl	imageCount	condition	conditionRaw	conditionBucket	listingStatus	category	sellerHash	sellerVerified	sellerType	isPromoted	sellerId	sellerName	isNew	changeType	previousPrice	priceDropPct	firstSeenAt	lastSeenAt	daysListed	lastPrice	gonePresumedSold	scrapedAt
iphone	true	OK	iphone	100	21197	true						<all listings found (full list)>	m2448114505	https://www.2dehands.be/v/telecommunicatie/mobiele-telefoons-apple-iphone/m2448114505-iphone-15-zwart-128gb	Iphone 15 zwart 128gb	- ik verkoop mijn iphone 15, met 128 gb. - Er is een kleine barst aan de bovenkant van de iphone, maar dit stoort niet en voel je ook niet, door de screenprotector die er op ligt. Ligte beschadigin...	0	FAST_BID		Ieper	België	2026-09-30	Vandaag	https://images.2dehands.com/api/v1/hz-twh-pro-listing/images/34a6dd14-4041-4e52-99f7-204cdfe33556?rule=ecg_mp_eps$_82.jpg	1		<condition (verbatim raw label)>	<condition (standard: new_with_tags/new/like_new/good/fair/unknown)>	<availability (standard: available/reserved/sold)>	1953	675c3e969cf01e88	false	private	true												2026-09-30T06:20:16.687Z

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.

How to filter

Every filter below is optional and off by default — leave it out and you get exactly the same rows as before. minPrice/maxPrice/priceType/includeKeywords/excludeKeywords already existed (the latter two match anywhere in the row — title, description, brand, condition, etc. — not just the title). This section adds conditions, availability, cities and sortBy. A filtered-out listing is dropped before it's billed — you never pay for a row you didn't get.

1. Only sold-as-new or like-new listings under 300 EUR:

{
  "searches": ["iphone"],
  "maxPrice": 300,
  "conditions": ["new", "like_new"]
}

conditions matches 2dehands' own Dutch condition labels (Nieuw → new, Zo goed als nieuw / Refurbished → like_new, Gebruikt → good, Niet werkend → fair; no attribute at all → unknown) — never guessed from the title. 2dehands has no "with tags" grade, so new_with_tags never matches anything here.

2. Cheapest first, in a named city:

{
  "searches": ["fiets"],
  "cities": ["gent"],
  "sortBy": "price_asc"
}

cities is a case-insensitive "contains" match against the listing's own city — no extra request. sortBy sorts the listings this run actually fetched, after filtering; leave it empty to keep 2dehands' own newest-first order (unchanged default).

3. Exclude a keyword (already-existing input, matches the whole row):

{
  "searches": ["laptop"],
  "excludeKeywords": ["defect", "onderdelen"]
}

availability also exists, but 2dehands' own feed already excludes sold listings and no sold value has ever been observed live, so it only ever offers all/available — a documented no-op kept for input-shape consistency with the rest of the portfolio.

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~2dehands-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~2dehands-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~2dehands-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 "2dehands 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 (2dehands-listing-lookup-delta), reports only listings that are genuinely new, whose price has dropped since the last run, or (if you turn it on) have disappeared — see below — 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, 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.

Sold signal and sell-through

Turn on "Alert on removed listings" and a listing your watchlist saw before, that has since disappeared from 2dehands/2ememain, comes back as an ordinary listing row with changeType: "gone" — no separate charge event, billed exactly like any other listing row. Gone listings are counted toward goneCount and sellThroughRate even with the checkbox off, so the rate is right from the first day a watchlist exists.

Honesty note. This platform never confirms a sale. A gone listing was most often sold, but it can also have been withdrawn, relisted under a new ID, put on hold, or edited so it no longer matches your search or price filters. gonePresumedSold narrows the guess: true only when the listing was seen on 2 or more consecutive runs (so it wasn't a one-off scrape glitch) and its last known price was at or under this run's median (in EUR) — cheap, well-established listings sell; expensive ones more often just get withdrawn or relisted.

How detection works. The API is always asked for sortBy=SORT_DATE&sortOrder=DECREASING (confirmed live), which this actor re-checks every run from the response's own echoed sort. Two ways a listing counts as gone:

• A complete fetch. Paging reached the real end of what the site reports for this search, with no blocked or failed page. Any remembered listing missing from it is gone, in any order.
• Feed position. On an incomplete (window-limited) fetch, a listing is gone only if its expected position, given how many listings arrived above it since the last run, still falls comfortably inside this run's window. Paid "Dagtopper" placements hold no position at all, so they can only be caught by a complete fetch. A listing near the bottom edge of the window is left alone that run — on doubt, the answer is always "still for sale".
• Presence is checked against everything this run actually fetched, before your price/price-type filters — a listing re-priced out of your filter is not gone.

Limits. No gone check on a first run, an empty fetch, a run where a page was blocked or failed, or a run whose fetch was both incomplete and couldn't be confirmed in date order. sellThroughRate is lifetime within the watchlist's 30-day-unseen / 5,000-listing bounds. listingId/sellerHash are shared across 2dehands.be and 2ememain.be, so a watchlist run under one site sees a listing gone the same way regardless of which site's URL you originally paired it with.

Example: track sell-through for a search.

{
  "searches": ["fiets"],
  "maxListingsPerSearch": 100,
  "deltaMode": true,
  "deltaName": "fiets-sold",
  "alertOnNew": false,
  "alertOnPriceDrop": false,
  "alertOnGone": true
}

Schedule it daily. With alertOnNew/alertOnPriceDrop off, the first run seeds the watchlist and returns only the summary row (listingCount: 0, nothing billed); sold signals start appearing from the second run on.

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.
• Switch "Site" to 2ememain.be for French-language titles and descriptions of the same listings; the listingId and sellerHash stay identical across both sites, so you can dedupe a mixed watchlist safely.
• 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.
• A BLOCKED status is unusual on this target (no anti-bot posture was observed on either host), but if you see one, lower "Max concurrency" and try again shortly.

vs. alternatives

	What it costs	What you get	Trade-off
This actor (2dehands-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 2dehands or 2ememain search, price, city, condition, seller hash, image, plus optional monitoring for new listings, price drops and a sold/sell-through signal, with a measured near-zero timeout rate	No server-side price-range API param was found, so min/max price filtering happens after fetching, not before
fatihtahta's 2dehands scraper (current Store leader, 41 users)	Comparable per-item pricing	A dump of listing data	Measured 16% timeout rate. This actor calls the platform's own JSON API directly instead of scraping a rendered page, and every verification run in this build finished in single-digit seconds
Doing it yourself	Your time, plus tracking the API's 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 the site returned an unexpected response (status: BLOCKED). Check the message column. None of these are billed.

What's the difference between 2dehands.be and 2ememain.be? Same marketplace, same listings, same sellers, different language front end (Dutch vs French) — confirmed live by comparing the identical listing ID and price across both sites' responses. listingId and sellerHash are identical across both, so you can safely combine or dedupe results if you ever search both.

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.

Is this a live check or a stored database? Live. Every run calls the platform's 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, which lives in your own actor's key-value store.

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.

Does it find sold listings? This platform never confirms a sale, so this actor detects "gone" (a listing your watchlist saw before that has since disappeared) and marks it gonePresumedSold when it was seen 2+ consecutive runs at or under that run's median price. Turn on "Alert on removed listings" to get those rows; sellThroughRate and goneCount are tracked either way. See "Sold signal and sell-through" above.

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 ("2dehands 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 2dehands or 2ememain.

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 the site's terms and your local law.

Related actors

• Marktplaats Scraper — the same search, built for 2dehands' Dutch sibling marketplace, marktplaats.nl.
• OLX Listing Lookup — the same keyword-search shape, for Poland's largest classifieds marketplace.