Belgium is a supported and actively expanding market. You get the same normalized schema, geo and city search, listing attributes and real-time webhooks as France — through one integration.
Belgium is a supported and expanding market on Stream.Estate. It uses the exact same API, schema and endpoints as France, so a single integration serves both — and grows as we deepen Belgian coverage over time.
Belgian listings are aggregated and normalized into the same property object: price, pricePerMeter, surface, room, bedroom, propertyType, transactionType, energy and pictures[], with each originating advert kept in the adverts[] array. Deduplication applies here too, so repeated postings resolve toward a single record.
Location search works through the shared endpoints. Use /cities and /public/location-autocomplete to resolve Belgian place names, filter by includedCities[] or includedZipcodes[], or search any point with lat/lon/radius. Real-time webhooks via POST /searches behave identically.
We are honest about depth: Belgium is newer than France and does not yet carry the same source breadth or French-specific administrative layers (there is no DVF-equivalent notarial dataset). Coverage is live and improving progressively. If you have specific Belgian regions or sources you need, tell us — it helps us prioritize.
Belgium uses the identical property object and endpoints as France. One integration covers both markets and extends as coverage grows.
Price, price-per-meter, surface, rooms, bedrooms, property type, transaction type, energy category and pictures[] — mapped to the same fields you already parse.
Resolve Belgian place names via /cities and /public/location-autocomplete, then filter with includedCities[] or includedZipcodes[].
Pass lat/lon/radius to search any point in Belgium; responses include locations{lat,lon} for mapping.
Repeated postings across sources resolve toward a single record, with each advert preserved in the adverts[] array.
POST /searches with an eventEndpoint to receive property.ad.create and ad.update.price events for Belgian searches, just like France.
Because Belgium shares the France schema, anything you build against GET /documents/properties works across both markets with the same code path.
Cross-border products. Serve France and Belgium from one integration — filter by market through city or geo parameters rather than maintaining separate connectors. See why an API beats web scraping.
Lead sourcing. Create a saved search with POST /searches and a webhook to catch new Belgian listings that match your criteria in real time. See lead generation.
Market monitoring. Track price changes and new supply in Belgian cities via ad.update.price and property.ad.create events. See market monitoring.
Valuation inputs. Use normalized surface, room, energy and price fields as model features; validate against local context as Belgian depth increases. See valuation.
# Houses for sale near a point in Belgium
curl -H "X-API-KEY: <api_key>" \
"https://api.stream.estate/documents/properties?lat=50.8503&lon=4.3517&radius=15&propertyTypes[]=1&transactionType=0&itemsPerPage=30"
Belgian coverage is aggregated and normalized into the same schema as our other markets and deduplicated across sources. Belgium is newer than France, so we do not publish a source count for it and it does not carry French-specific administrative layers such as a DVF-equivalent. Coverage is live and expanding — reach out if you need specific regions prioritized.
Free trial, full documentation, real-time webhooks. One integration for every market we cover.