AnchorRun your own real estate listing database

Immoteur supplies selected source listings through API access, exports, and live delivery services. Your team operates the receiver, durable queue, worker, database, and the CRM, BI, or product workflows built on that data.

Immoteur supplies the selected source deliveries and their contracts. Your team operates the systems that receive, transform, store, and use them.

Store each delivered listing snapshot separately from your scores, notes, CRM states, BI transformations, and product data. A refresh can then update the delivered fields without erasing work your team has added.

Classified.id identifies a source listing. propertyId identifies an Immoteur property grouping that can represent a programme or multiple dwellings, so neither identifier guarantees a history for one dwelling.

Before the Full bootstrap, make the receiver ready and activate a compatible classified-notification-single or classified-notification-batch service with onlyNew=false. Keep that live service active during and after the Full bootstrap.

Persist or durably enqueue the complete received delivery before returning 2xx, then process it in an asynchronous worker. Live delivery is at least once and unordered, so make duplicate and late processing safe.

Run a Delta export on a regular seven-day cadence to reconcile the selected dataset. It uses a successful, compatible baseline created no more than eight days earlier. When none is available, the requested Delta export can be delivered as a Full export instead.

An item absent from a later export is not automatically a deletion instruction for your database.

Read historical property data exports for the Full and Delta workflow, and real estate webhooks for receiver safety. The local data mirror guide↗, webhook delivery guide↗, and classified-export API reference↗ contain the detailed delivery contracts.

Create an account at Immoteur sign-up when your team is ready to configure data access.