Skip to main content
A 2xx response acknowledges a webhook delivery. A non-2xx response or transport failure does not acknowledge it.
If your endpoint restricts source IPs, allowlist the following Immoteur egress IPs before testing:51.38.208.80 and 54.37.96.165.

​
Receive a webhook safely

Keep the HTTP handler small. Do not run slow business logic, enrichment, or downstream API calls before acknowledging the request.
  1. Read X-Immoteur-Event-Id and persist or durably enqueue the event before acknowledging it.
  2. Return 204 No Content or another 2xx response as soon as that work is safe.
  3. Process the event in your own worker or queue after the HTTP response. The queue and worker are your integration architecture, not an Immoteur service.

​
Timeouts

Immoteur currently applies a 5 seconds connection timeout and a 5 seconds request timeout. A receiver that waits for slow work can time out before it acknowledges the delivery. Persist or enqueue first, then return a successful response quickly.

​
Read the delivery headers

Do not assume that export chunks have the same event-ID stability as classified notifications.

​
Retries and circuit breaking

A non-2xx response, including a 4xx, is not a successful acknowledgement. An export can have multiple delivery attempts and chunks; do not assume a fixed chunk size or strict order. Immoteur applies the appropriate retry policy after an unacknowledged delivery. When 1,000 retry events are in flight for one service, its circuit opens for 10 minutes. Deliveries for that service are skipped during the cooldown and are not automatically replayed. Configure the endpoint and filters in Configure Immoteur webhooks. Use Mirror classified data for the full export, live notification, and delta-export integration flow. Use API reliability for API rate-limit headers.