# Zenga.hu HU Property Listings (`bakos_bence/zenga-listings`) Actor

Scrape zenga.hu (OTP Otthon) sale/rent listings — HUF prices, private/agency filter. Unofficial — not affiliated with Zenga or OTP.

- **URL**: https://apify.com/bakos\_bence/zenga-listings.md
- **Developed by:** [Bakos Bence](https://apify.com/bakos_bence) (community)
- **Categories:** Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.25 / 1,000 results

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### What does Zenga.hu Listings Scraper do?

**Scrape [zenga.hu](https://www.zenga.hu/) (OTP Otthon) sale and rent listings** via the site’s **public JSON API** — **HUF prices with currency, area, rooms, city, and listing URLs**. Filter **private-person** ads vs agencies. Click **Start** on the prefilled multi-city private search (`maxResults` 5).

**Unofficial.** This Actor is **not affiliated with, endorsed by, or maintained by Zenga or OTP**. Seller **names, phones, and emails are never written** to the dataset. `agencyName` is office/franchise names only when the listing is an agency.

**Dashboards:** connect **Power BI**, **Tableau**, **Looker Studio**, or **Qlik** to the dataset API — see *Export to Power BI, Tableau, Looker Studio & Qlik* near the end. **AI agents:** paste this Actor’s Store page URL into an Apify-capable agent (MCP / Claude / Cursor with Apify), create an Apify account and API token once, and the agent can run the Actor and wire up the output.

#### Why use this Zenga scraper?

- 🏠 Public `POST /api/rels/v1/adverts/search` + detail GETs — **no browser, no Unblocker**
- 👤 `sellerType`: `private` · `agency` · `all` (private uses `contact.isRealEstateAgency === false`)
- 💶 HUF prices kept **with currency**
- 🛡️ Apify **Residential + HU** proxy (datacenter/auto soft-blocks the JSON API)

#### How to scrape zenga.hu listings

1. Open this Actor in [Apify Console](https://console.apify.com/).
2. Click **Start** on the prefilled private search (`maxResults` 5).
3. Keep Residential HU proxy on.
4. Export the dataset or pull via API.

```json
{
  "sellerType": "private",
  "discoveryMode": "search",
  "searchTexts": ["elado+lakas+budapest", "elado+lakas+szeged"],
  "maxResults": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "HU"
  }
}
```

#### How much does it cost?

**Pay per event (PPE):** Actor start + each listing **result**. On Free, results are about **$2.50 / 1,000**; paid plans are lower (see the Pricing tab). Platform usage is included. Prefer Residential HU — Unblocker is unnecessary for this API and costs far more.

#### Input

| Field | Description |
|-------|-------------|
| `sellerType` | `private` (default) · `agency` · `all` |
| `discoveryMode` | `search` (default) or `sitemap` |
| `searchTexts` | e.g. `elado+lakas+budapest` |
| `maxResults` | Listing cap (prefill 5) |
| `fetchDetails` | Required for private/agency filter |
| `proxyConfiguration` | Apify Residential HU recommended |

#### Sample output

```json
{
  "listingId": 9089934,
  "title": "Eladó családi ház, Abony",
  "url": "https://www.zenga.hu/ingatlan/.../9089934",
  "price": 45900000,
  "currency": "HUF",
  "pricePerSquareMeter": 1973291,
  "saleType": "Sale",
  "category": "House",
  "floorAreaSize": 120,
  "numberOfRooms": 4,
  "address": "Abony",
  "city": "Abony",
  "sellerType": "private",
  "isRealEstateAgency": false,
  "agencyName": null,
  "scrapedAt": "2026-09-03T12:00:00+00:00",
  "source": "zenga.hu"
}
```

#### Tips

- Soft-block signature: empty search titled “Eladó ház országosan” or detail body `{}` → rotate proxy / stay on Residential HU.
- Private mode fetches details (search cards lack the agency flag).
- For bulk inventory, `sellerType=all` + many search shards or `discoveryMode=sitemap`.

#### FAQ

##### Do I need Unblocker?

No. The JSON API works with normal HTTP plus Apify Residential HU. Unblocker is much more expensive and not required.

##### Are seller phones included?

No. Named-person phones, emails, and private-seller names are never emitted. Agency office names may appear on agency rows.

##### Private vs agency — how is it classified?

Detail payload `contact.isRealEstateAgency` plus agency fields. Search cards alone cannot filter seller type.

#### Related Actors

| Actor | Use together when… |
|-------|-------------------|
| [Zenga.hu HU Property Listings](https://apify.com/bakos_bence/zenga-listings) | *(this Actor)* — zenga.hu JSON API → listing rows |
| [Ingatlan.com HU Property Listings](https://apify.com/bakos_bence/ingatlan-com) | You also need Hungary’s #1 portal (ingatlan.com) |
| [Otodom.pl Listings](https://apify.com/bakos_bence/otodom-listings) | You compare HU comps with Poland’s Otodom |

Profile: [bakos\_bence on Apify](https://apify.com/bakos_bence)

**Actor ID:** `bakos_bence/zenga-listings`

#### Export to Power BI, Tableau, Looker Studio & Qlik

After a run, rows live in an Apify **dataset**. You can download JSON/CSV/Excel from the Dataset tab, or point BI tools at a **CSV URL** that refreshes when you scrape again.

**Prefer the token in the URL** (`token=`) — most tools only need “open this link as CSV”, with no custom headers.

##### Build a refreshable CSV URL

1. In Apify Console, open **Settings → Integrations** and copy an API token.
2. Save this Actor as a **Task** (optional but best for dashboards), run or **schedule** it once so there is a successful run.
3. Use the **latest successful task run** URL (replace `TASK_ID` and `YOUR_TOKEN`):

```text
https://api.apify.com/v2/actor-tasks/TASK_ID/runs/last/dataset/items?format=csv&clean=true&status=SUCCEEDED&token=YOUR_TOKEN
```

Or, from any finished run, open the **Dataset** tab, copy the dataset ID, and use:

```text
https://api.apify.com/v2/datasets/DATASET_ID/items?format=csv&clean=true&token=YOUR_TOKEN
```

Anyone with that URL can read the data — treat it like a password. For recurring dashboards, prefer the `actor-tasks/…/runs/last/…` form so refresh always hits the newest successful scrape.

##### Power BI

1. Open Power BI Desktop → **Home** → **Get data** → **Web**.
2. Paste the CSV URL (including `token=`).
3. When asked how to sign in, choose **Anonymous** → **Connect**.
4. Confirm the preview is a table (CSV). **Load** or **Transform data** as needed.
5. Publish / schedule refresh in the Power BI service using the same URL (task `runs/last` keeps it current after each scrape).

`401`: token missing/wrong, or you did not pick **Anonymous**.

##### Tableau

1. Install Tableau’s **REST API** connector from Tableau Exchange (Desktop **2023.3+**).
2. **Connect** → **To a Server** → **REST API**.
3. Paste the CSV URL (including `token=`). Set response format to **CSV**.
4. If the connector asks for auth and the token is already in the URL, leave credentials empty / anonymous; otherwise paste the same token as a Bearer access token.
5. Create an **extract**. Refresh the extract after scheduled Task runs (or point at `runs/last` so each refresh loads the latest success).

Plain **Text file** connect still works if you download CSV from the Dataset tab once — use REST when you want repeatable refresh.

##### Looker Studio

Looker Studio has no strong built-in “private CSV API” connector. Use Google Sheets as the bridge:

1. Create a Google Sheet. In **A1** enter:

```text
=IMPORTDATA("https://api.apify.com/v2/actor-tasks/TASK_ID/runs/last/dataset/items?format=csv&clean=true&status=SUCCEEDED&token=YOUR_TOKEN")
```

2. Wait until columns fill (Sheets refreshes IMPORTDATA periodically).
3. In Looker Studio → **Create** → **Report** → **Google Sheets** → select that spreadsheet / tab.
4. Build the report. After each Actor/Task run, refresh the Sheet (or wait for IMPORTDATA) then refresh the Looker data source.

One-off alternative: Dataset tab → download CSV → Looker Studio **File upload**.

##### Qlik

**REST connector** (refreshable):

1. In Qlik Cloud / Qlik Sense → **Add data** → **REST** (or create a REST connection in the Data load editor).
2. URL = the CSV URL including `token=`. Method **GET**.
3. Set the expected response type to **CSV** (or use `format=json` and JSON mode).
4. **Test connection**, pick the table, **Add** / **Load**.
5. **Reload** the app after scheduled scrapes; with `runs/last`, each reload pulls the latest successful dataset.

**Files:** Dataset tab → download CSV → **Add data** → upload the file (fine for a single snapshot).

# Actor input Schema

## `sellerType` (type: `string`):

private = magánszemély only (contact.isRealEstateAgency=false). agency = offices only. all = every listing.

## `discoveryMode` (type: `string`):

search = paginate /api/rels/v1/adverts/search (fast). sitemap = walk listing IDs from public sitemaps (broader, more requests).

## `searchTexts` (type: `array`):

Zenga textSearch strings (e.g. elado+lakas+budapest). Used when discoveryMode=search.

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

Stop after this many matching dataset rows.

## `pageSize` (type: `integer`):

Cards per search page (max 100).

## `concurrency` (type: `integer`):

Parallel advert detail fetches. Higher = faster, more chance of soft-blocks.

## `sleepSecs` (type: `number`):

Polite delay per detail request thread.

## `fetchDetails` (type: `boolean`):

Required for private/agency filter. Only disable when sellerType=all and you want card-only fields.

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

Use Apify Residential + HU. Datacenter/auto soft-blocks the JSON API (empty search / {}). Avoid UNBLOCKER — not needed and much more expensive.

## Actor input object example

```json
{
  "sellerType": "private",
  "discoveryMode": "search",
  "searchTexts": [
    "elado+lakas+budapest",
    "elado+lakas+szeged",
    "elado+lakas+debrecen"
  ],
  "maxResults": 5,
  "pageSize": 20,
  "concurrency": 6,
  "sleepSecs": 0.2,
  "fetchDetails": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "HU"
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

Dataset items

# 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 = {
    "sellerType": "private",
    "discoveryMode": "search",
    "searchTexts": [
        "elado+lakas+budapest",
        "elado+lakas+szeged",
        "elado+lakas+debrecen"
    ],
    "maxResults": 5,
    "pageSize": 20,
    "concurrency": 6,
    "fetchDetails": true,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "HU"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("bakos_bence/zenga-listings").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 = {
    "sellerType": "private",
    "discoveryMode": "search",
    "searchTexts": [
        "elado+lakas+budapest",
        "elado+lakas+szeged",
        "elado+lakas+debrecen",
    ],
    "maxResults": 5,
    "pageSize": 20,
    "concurrency": 6,
    "fetchDetails": True,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "HU",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("bakos_bence/zenga-listings").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 '{
  "sellerType": "private",
  "discoveryMode": "search",
  "searchTexts": [
    "elado+lakas+budapest",
    "elado+lakas+szeged",
    "elado+lakas+debrecen"
  ],
  "maxResults": 5,
  "pageSize": 20,
  "concurrency": 6,
  "fetchDetails": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "HU"
  }
}' |
apify call bakos_bence/zenga-listings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bakos_bence/zenga-listings"
        }
    }
}

```

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/dOfHLH7inESgPI2ND/builds/1kyTbbkIoiTMtzCvr/openapi.json