Skip to main content
Choose the endpoint from the information already available to your integration. A classified is a source listing; a property groups listings for the underlying real-estate asset or, where the source advert has that scope, a whole programme. The generated API reference remains the source for parameters and response schemas.

​
Select an endpoint

Use a direct retrieval endpoint when you already know an identifier. Use property search when you need a filtered, paginated set of properties.

​
Understand programme classification and property scope

A propertyId identifies an Immoteur property group; it does not guarantee that every grouped listing represents one individual dwelling. A source Classified can describe a whole programme comprising multiple units, and a propertyId can therefore legitimately group that programme with listings for different units. Different prices, areas, or room counts in such a group are not the price history of one dwelling. A Classified can itself be the programme advert, so its identifier alone does not guarantee a unit-level history. property.isNew and property.isProgram are independent optional booleans. isNew is a source-based classification that a property is described as new or recently built. isProgram is a source-based classification for a programme, off-plan, or under-construction offering; it can apply to a whole programme comprising multiple units or to an individual unit. For a Classified, isProgram follows fixed precedence. Rental classifieds return false before an explicit source boolean is considered. For other transactions, an explicit source boolean wins. Without an explicit boolean, a known non-professional publisher returns false before URL or text inference. A professional or unknown publisher remains unknown when the remaining programme evidence is insufficient. Both fields can be true. On a Classified, each field reflects the source classification; on a Property, Immoteur returns a value only when the known values of all currently linked classifieds agree. When source evidence is absent, or known values conflict, the response omits the field; an explicit false remains false.

​
Report an issue

Use POST /issues to report incorrect property or listing information, a listing whose status should be different, a grouping problem, or another observed problem. A report records the problem; it does not change the affected resource. Report an issue through the API helps you choose the report and check the selected IDs. A data report concerns one Property or one Classified listing, while an other report can concern Properties, Classified listings, both, or neither. Create an issue report has nine named request examples and every field requirement; replace its synthetic UUIDs with IDs your credentials can access.

​
Look up a listing or property from its URL

Choose the lookup based on the resource your integration needs. Provide the listing URL through the url query parameter. Use GET /classifieds/lookup to retrieve the source listing, or use GET /properties/lookup to retrieve the grouped property associated with that listing.
To maintain a local copy of the selected classified stream instead of querying one resource at a time, use Mirror classified data.

​
Search properties

The request body requires page, transactionType, and propertyTypes. Add optional filters only when they match the result you need.
Use propertyIsProgram to filter property-search results by their property-level programme classification. The request field remains propertyIsProgram, while API responses use property.isProgram; a property with no returned programme classification matches neither explicit filter value. There is no isNew search filter.

​
Continue through property search results

Read meta.nextPage from each POST /properties/search response. When it contains a page number, send the same search request with that value as page. Stop when meta.nextPage is null. If a request is rejected or limited, see API reliability. Open the generated API reference for the exact lookup parameters and response schemas.