Configure Immoteur webhooks

Configure a service when your integration needs classified data without polling the API. In the Immoteur dashboard, open API → Webhooks and set the receiver URL for the service.

​

Choose the updates to receive

Immoteur sends a classified notification when a classified is created or when an eligible normalized field changes. A meta.lastSeenAt-only revisit is captured for delta-export reconciliation and does not create a direct live notification. Use meta.lastModifiedAt to identify the latest normalized update and meta.lastSeenAt to identify the latest revisit. There is no periodic keep-alive webhook.

​

Configure the endpoint

Create the service in API → Webhooks in the Immoteur dashboard. Use an HTTPS endpoint that your service controls.

​

Filter the stream

Each service has one filter object. Choose the filter type that matches the scope your integration is allowed to receive. The exact keys depend on that type: Every required key must be present. transactionType is always required and non-null, and a geographic filter requires a non-empty locationDepartments list. Other required keys may use null only where the schema permits it. For a global filter, nullable propertyTypes, publisherType, and sourceDomains values leave those dimensions unrestricted; transactionType still defines the scope.

​

Choose the payload type

Each service has exactly one payload type. Use separate services when your integration needs both kinds of delivery. For classifieds exports, exportType identifies the effective type delivered for the entire export: full for a Full export and delta for a Delta export. Its value is the same on every data batch and terminal completion message. When a requested Delta export falls back, deliveries use full; the receiver payload does not include the requested mode or the fallback reason. Use a classifieds service for Full export baselines and Delta export reconciliation. It must be a separate, compatible service from the classified live-event service, although both services may send to the same receiver URL. An export can contain multiple deliveries. Do not rely on a fixed item count or delivery order. See Mirror classified data for the full baseline, live update, and delta-reconciliation flow, then read Webhook delivery, retries, and idempotency before implementing the receiver.