# 2dehands Scraper: Belgium New Listing Alerts (`accountable_eel/2dehands-listing-lookup`) Actor

2dehands scraper by keyword: run a search on 2dehands.be (or its sibling 2ememain.be) and get one row per listing, including price, city, condition, seller hash and link, plus optional alerts for new listings and price drops. No login required. Pay per listing returned; empty searches are free.

- **URL**: https://apify.com/accountable\_eel/2dehands-listing-lookup.md
- **Developed by:** [Adrian Voss](https://apify.com/accountable_eel) (community)
- **Categories:** E-commerce, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 listing returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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, 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 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) |
| `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`, 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.

### 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:
   ```bash
   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

```json
{
  "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 | 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 | <search> | <listings returned> | <total matching> | <more results were available> | <new listings this run> | <price drops this run> | \<all listings found (full list)> | <listing id> | <listing link> | <title> | <description> | \<price (eur)> | <price type> | <city> | <country> | \<posted (date)> | \<posted (as the site words it)> | <image> | <photo count> | <condition> | <category id> | \<seller (anonymous hash)> | <seller verified> | <seller type> | <promoted listing> | \<seller id (only with seller info on)> | \<seller name (only with seller info on)> | \<is this listing new?> | <change type> | \<previous price (eur)> | \<price drop %> | <first seen on a run> | 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.

```bash
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 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`, 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.
- 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 and price drops, 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.

**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](https://apify.com/accountable_eel/marktplaats-listing-lookup) — the same
  search, built for 2dehands' Dutch sibling marketplace, marktplaats.nl.
- [OLX Listing Lookup](https://apify.com/accountable_eel/olx-listing-lookup) — the same
  keyword-search shape, for Poland's largest classifieds marketplace.

# Actor input Schema

## `searches` (type: `array`):

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/. You're only charged for the ones we actually find — a miss costs nothing.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

## `maxResults` (type: `integer`):

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `site` (type: `string`):

2dehands.be (Dutch) or 2ememain.be (French) -- same marketplace, same listings, same sellers, different language front end. A pasted search URL's own site always wins over this setting.

## `maxListingsPerSearch` (type: `integer`):

This platform returns up to 100 listings per request (the real, confirmed ceiling -- 101 is rejected); this actor pages automatically above that, up to 1000 per search. You pay per listing returned, so this is also your budget control.

## `minPrice` (type: `integer`):

Optional. Drop listings priced below this. Leave empty for no minimum. Applied after fetching (no confirmed API price-range parameter).

## `maxPrice` (type: `integer`):

Optional. Drop listings priced above this. Leave empty for no maximum. Applied after fetching (no confirmed API price-range parameter).

## `priceType` (type: `string`):

Optional. Keep only listings of this price type. FIXED, MIN\_BID, FAST\_BID and SEE\_DESCRIPTION were observed live; BID, FREE, ASKING, TRADE and RESERVED are this platform's other documented values (shared with marktplaats-listing-lookup, same API). Applied after fetching.

## `postcode` (type: `string`):

Optional. A Belgian postcode (e.g. "1000" for central Brussels) -- confirmed live to change every listing's distance and re-center results. Leave empty to search all of Belgium.

## `distanceKm` (type: `integer`):

Only used when "Postcode to search near" is set. Any positive number works on the API.

## `deltaMode` (type: `boolean`):

Turns this actor into a monitor. A listing counts as new when its listing ID hasn't been returned by a previous run of the same watchlist; a price drop counts when a previously-seen listing's price has fallen (see "Minimum price drop" below). Already-reported listings are dropped before you're billed, so a run with nothing new or dropped costs only the run fee. The first run has nothing to compare against, so it returns and remembers everything; from the second run on you get only what changed.

## `deltaName` (type: `string`):

Leave empty and we derive one from this run's filters, so two schedules with different filters keep separate memories. Type your own name to keep one memory across a filter change, or to have two schedules share one.

## `alertOnNew` (type: `boolean`):

Part of "Alert on" (split into two checkboxes so the Console can render it as a plain toggle pair). On by default.

## `alertOnPriceDrop` (type: `boolean`):

Part of "Alert on". On by default.

## `minPriceDropPct` (type: `integer`):

Only fires for a FIXED-price or ASKING-price listing where both the old and new price are set (never for bids, free, or "see description" listings). Default 5%.

## `skipFirstRun` (type: `boolean`):

On: the run that first starts a watchlist banks every listing silently -- no rows, no charge -- instead of reporting everything that already existed as "new". Off (default): the first run returns everything it finds, all marked new.

## `includeSellerInfo` (type: `boolean`):

Off by default. On: adds the seller's raw ID and display name to every row, in addition to the always-on anonymous seller hash. Turning this on makes you responsible for having a lawful reason to process that personal data.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each listing found gets its own row instead of being grouped under its search. You're still only charged once per search, no matter how many rows it produces.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

## `proxyConfiguration` (type: `object`):

Apify Proxy config. Residential recommended for anti-bot-sensitive targets.

## Actor input object example

```json
{
  "searches": [
    "iphone"
  ],
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "site": "2dehands",
  "maxListingsPerSearch": 100,
  "priceType": "",
  "postcode": "",
  "deltaMode": false,
  "deltaName": "",
  "alertOnNew": true,
  "alertOnPriceDrop": true,
  "minPriceDropPct": 5,
  "skipFirstRun": false,
  "includeSellerInfo": false,
  "columns": [
    "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"
  ],
  "expandRows": true,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searches": [
        "iphone"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/2dehands-listing-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searches": ["iphone"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/2dehands-listing-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searches": [
    "iphone"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/2dehands-listing-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/2dehands-listing-lookup"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/L007K0AjwMx9gpMvH/builds/UbGz4KXhZU1R5H4l2/openapi.json