# Spotto Scraper - Belgian Commercial Property + Zoning (`studio-amba/spotto-scraper`) Actor

Scrape commercial property listings from Spotto.be, the government-backed Flanders property platform: offices, retail, horeca, industrial and land, with Flemish zoning (bestemmingsplan), permit and flood-risk data no other portal exposes.

- **URL**: https://apify.com/studio-amba/spotto-scraper.md
- **Developed by:** [Studio Amba](https://apify.com/studio-amba) (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.20 / 1,000 result scrapeds

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/platform/actors/running/actors-in-store#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

## Spotto Scraper — Belgian Commercial Property with Zoning Data

Scrape commercial property listings from [Spotto.be](https://www.spotto.be), the government-backed property platform for Flanders (Belgium). Offices, retail, horeca, industrial buildings and land, for rent and for sale, as clean structured JSON.

What sets Spotto apart from every other Belgian portal is the Flemish urban-planning disclosure on its listings. This actor captures all of it:

- **Zoning designation** (bestemmingsplan): the official zoning code (Wg = Woongebied, Igb = Industriegebied voor bedrijven, Ag = Agrarisch gebied, ...) plus the Dutch label as Spotto displays it
- **Permit status**: urban-planning permit (stedenbouwkundige vergunning), subdivision permit (verkavelingsvergunning), registered construction offenses and subpoenas
- **Flood risk** (watertoets): flood-prone classification plus the Flemish P-score (parcel) and G-score (building)
- **Preemption rights** (voorkooprecht) and the soil certificate (bodemattest) result

For site selection, due diligence or land sourcing, this is data you would otherwise dig out of Flemish government geoportals parcel by parcel.

### What you get per listing

Address down to street and house number, NIS municipality code, coordinates, price with currency and unit, monthly charges, floor and plot surface, EPC label and score, construction and renovation year, full Dutch description, agency name, photo URL, publication date and the listing URL. Plus the zoning and permit block described above.

Prices on request are normal in commercial property. When a seller hides the price, the `price` field is `null` — the actor never fakes a number.

### How to scrape Spotto data

1. Pick a **location**: a municipality name ("Gent", "Leuven", "Antwerpen") or a 4-digit postal code ("9000"). Leave empty for all of Belgium.
2. Pick a **segment**: office (kantoor), retail (winkel), horeca, industrial (industrie), land (grond), or all commercial property at once.
3. Pick a **listing type**: for rent (te huur), for sale (te koop), or both.
4. Set **maxResults** and run.

Example input:

```json
{
    "searchQuery": "Gent",
    "segment": "office",
    "listingType": "rent",
    "maxResults": 100
}
```

Example output record:

```json
{
    "title": "Kantoren te huur in voormalige directeurswoning in Gent",
    "segment": "office",
    "subtype": "office",
    "listingType": "rent",
    "price": 2000,
    "currency": "EUR",
    "priceUnit": "EUR/month",
    "surface": 240,
    "street": "Wondelgemkaai",
    "houseNumber": "8",
    "postalCode": "9000",
    "locality": "Gent",
    "municipalityCode": "44021",
    "latitude": 51.0892,
    "longitude": 3.7267,
    "epcLabel": "B",
    "zoningCode": "Wg",
    "zoningLabel": "Woongebied",
    "permitStatus": "PermitAvailable",
    "floodProneType": "notFloodProne",
    "agencyName": "Oranjeberg Vastgoed",
    "url": "https://www.spotto.be/nl/p/te-huur/9000-gent/kantoor-wondelgemkaai-8---v0/Nx5OaBzReUo7nwje-TrmlQ",
    "source": "spotto.be"
}
```

### Segments

| Segment | Dutch | Covers |
| --- | --- | --- |
| `office` | kantoor | Offices and business centers |
| `retail` | winkel | Shops, commercial spaces, trading premises |
| `horeca` | horeca | Cafes, restaurants, hotels |
| `industrial` | industrie | Industrial buildings, warehouses, logistics |
| `land` | grond | Commercial land and building plots |
| `all-commercial` | bedrijfsvastgoed | All of the above in one run |

The `land` segment includes generic building plots, because Spotto lists most plots under its generic land type rather than the commercial-land type. Every record carries both the normalized `segment` and Spotto's own `propertyType`, so you can filter either way.

### Locations

Location filtering is municipality-level (the merged fusiegemeente). A sub-municipality like Kessel-Lo resolves to Leuven, and Sint-Amandsberg to Gent. Both Dutch names and postal codes work. Spotto is strongest in Flanders — that is its mandate — but also carries listings in Brussels and Wallonia.

### The zoning fields, briefly

Flemish sellers must disclose urban-planning information when advertising property. On Spotto that disclosure is structured, and this actor passes it through:

| Field | Meaning |
| --- | --- |
| `zoningCode` / `zoningLabel` | Zoning designation from the regional land-use plan, e.g. `Wg` / Woongebied (residential), `Igb` / Industriegebied voor bedrijven (industrial) |
| `permitStatus` | Whether an urban-planning permit is available, requested, or unavailable |
| `subdivisionPermit` | Subdivision (verkaveling) permit status, when the plot is part of one |
| `constructionOffense` | Registered construction offense, if any |
| `floodProneType` | Watertoets classification: not flood prone, possibly, or effectively flood prone |
| `floodScoreParcel` / `floodScoreBuilding` | The Flemish P-score and G-score (A to D) |
| `hasPreemptionRights` | Whether a legal preemption right applies |
| `soilCertificate` | Soil certificate result type |

Disclosure completeness varies by seller. In practice roughly 60-70% of listings carry a zoning code and flood data; the rest return `null` because the seller left the field empty at the source. The actor reports exactly what Spotto exposes.

### Cost

The zoning block lives on each listing's detail endpoint, so with **Fetch zoning and detail data** enabled (the default) the actor makes roughly one request per listing, plus one per unique agency for the agency name. A 100-listing run is therefore on the order of 100-150 requests. With the toggle off, the actor only reads search pages — one request per 200 listings — and the zoning, description, EPC-score and agency fields stay `null`.

Pricing is per result. Note that a run's usage cost only settles after the run reports SUCCEEDED — reading the cost mid-run undercounts it.

### Typical uses

- **Site selection**: find retail or horeca space in a specific municipality with the zoning to match
- **Land sourcing**: building plots with subdivision-permit status and flood scores included
- **Due diligence**: pull the urban-planning disclosure for a market segment in one run instead of parcel-by-parcel geoportal lookups
- **Market monitoring**: track new commercial supply and asking prices per municipality
- **Lead generation**: listings carry the agency name, so you know who markets what where

### Input reference

| Field | Type | Default | Notes |
| --- | --- | --- | --- |
| `searchQuery` | string | empty (all of Belgium) | Municipality name or 4-digit postal code |
| `segment` | string | `all-commercial` | `office`, `retail`, `horeca`, `industrial`, `land`, `all-commercial` |
| `listingType` | string | `all` | `rent`, `sale`, `all` |
| `fetchZoningDetails` | boolean | `true` | Off = list-level fields only, far fewer requests, no zoning block |
| `maxResults` | integer | 100 | Hard cap on returned listings, maximum 50,000 |
| `proxyConfiguration` | object | BE residential | Spotto served plain requests without blocks during testing |

### Data quality notes

- `surface` (indoor floor area) is empty on most commercial listings at the source; `landSurface` is filled more often. This mirrors Spotto itself.
- Long runs are migration-safe: progress is checkpointed, and a resumed run continues where it left off without duplicating listings.
- If Spotto ever ignores a location or segment filter (an API change), the actor fails loudly instead of returning country-wide data as if it were filtered.

### Related actors

- [Immoweb Commercial Scraper](https://apify.com/jelle.desramaults/immoweb-commercial-scraper) — commercial listings on Belgium's largest portal, same output field names
- Ideal together: Immoweb for national coverage and volume, Spotto for the zoning and permit data no other portal has

# Actor input Schema

## `searchQuery` (type: `string`):

Belgian municipality name ('Gent', 'Leuven', 'Antwerpen') or a 4-digit postal code ('9000'). Filtering is municipality-level: a sub-municipality like Kessel-Lo resolves to its merged municipality (Leuven). Leave empty to search all of Belgium.

## `segment` (type: `string`):

Commercial segment. 'Land (grond)' covers commercial land plus building plots (Spotto lists most plots under the generic land type). 'All commercial' runs Spotto's full bedrijfsvastgoed set in one go.

## `listingType` (type: `string`):

For rent (te huur), for sale (te koop), or both in one run.

## `fetchZoningDetails` (type: `boolean`):

LOAD-BEARING: this fetches each listing's detail page and adds the Flemish urban-planning disclosure (zoning/bestemmingsplan code, permit status, flood scores, preemption rights, soil certificate) plus description, EPC score, construction years and agency name. Costs roughly one extra request per listing. Off = list-level fields only, one request per 200 listings.

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

Maximum number of listings to return. Spotto carries roughly 45,000 publications in total; a typical commercial search matches a few hundred to a few thousand.

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

Proxy settings. Spotto's API served plain requests without blocks during recon; Belgian residential proxy is prefilled as the safe default.

## Actor input object example

```json
{
  "searchQuery": "Gent",
  "segment": "office",
  "listingType": "rent",
  "fetchZoningDetails": true,
  "maxResults": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "BE"
  }
}
```

# 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 = {
    "searchQuery": "Gent",
    "segment": "office",
    "listingType": "rent",
    "maxResults": 20,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "BE"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("studio-amba/spotto-scraper").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 = {
    "searchQuery": "Gent",
    "segment": "office",
    "listingType": "rent",
    "maxResults": 20,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "BE",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("studio-amba/spotto-scraper").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 '{
  "searchQuery": "Gent",
  "segment": "office",
  "listingType": "rent",
  "maxResults": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "BE"
  }
}' |
apify call studio-amba/spotto-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,studio-amba/spotto-scraper"
        }
    }
}

```

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/TNIUSiVo51pK06p2i/builds/6ZkZYVhIlIWWFFjcG/openapi.json