AnchorFrench property listings API for real estate applications

Use the Immoteur REST API when your application needs a filtered property search, a known resource, or a listing URL lookup. The API works with both Classified and Property resources, so a team can keep source-listing evidence alongside a grouped property view. Account access remains part of every response contract.

AnchorChoose search, retrieval, or URL lookup

Choose search when the work starts with a defined market segment, retrieval when your system already has an Immoteur identifier, and URL lookup when it starts from a source-listing URL.

The API keeps the two resource types connected, so an application can begin with a source listing and retrieve its Property group, or begin with a Property and inspect related Classifieds.

AnchorSearch and retrieve a Property group

Use POST /properties/search for a defined segment. It requires page, transactionType, and propertyTypes; add location, price, feature, source-domain, or text filters only when they answer the product or analysis question. Use meta.nextPage to continue the same search until it is null.

Use GET /properties/{id} when you have a Property identifier, or GET /properties/lookup when a source-listing URL is the input. A Property groups related listings for an underlying asset or, where a source listing has that scope, a whole programme.

A property-search workspace can turn a defined segment into a grouped view of source listings.

A property-search workspace filters sale apartments in Paris department 75 under €700,000, displays a 52.5 square metre three-room property at €650,000 with an apartment image, and groups three source listings from seloger.com, bienici.com, and orpi.com, marked available, available, and removed.

AnchorRetrieve a Classified source listing

Use GET /classifieds/{id} when you have the source-listing identifier, or GET /classifieds/lookup when you start with its URL. A Classified is one source listing or advertisement, so it keeps that publication and its source URL separate from the Property group.

Use the Classified snapshot when your application needs its current status and transaction fields, including the current price and, when present, the initial price. A Classified can itself describe a whole programme, so neither a Classified ID nor a Property ID proves a one-dwelling identity or a complete price history for one dwelling.

A listing-review workspace can show one source listing alongside its URL, status, and transaction fields.

A listing-review workspace displays one seloger.com source listing marked available, with a current price of €650,000, an initial price of €680,000, 52.5 square metres, 3 rooms, a View source listing action, and an apartment image.

AnchorKeep access scope in the request path

Call GET /auth after creating a token to inspect meta.dataAccessLimit. Department, SIREN, and SIRET access limits are applied to the integration. Request filters can narrow results but cannot extend configured access.

Build that limit into your own UI, analysis, and acceptance tests. A valid request does not assure data outside the configured access scope.

AnchorBuild against the published API contract

Use the public Mintlify reference for POST /properties/search to verify its published request and response examples. Read the API quickstart to validate authentication and make the first request, then read the API resource guide for current schemas, relations, and filters.

A screenshot of the Mintlify reference for POST /properties/search, showing documented request and response examples.

Create an account at Immoteur sign-up when your implementation scope is ready.