Webhooks

Webhooks push events to your endpoint the moment they happen — no polling. Subscribe once, react to changes across your portfolio.

What you can subscribe to

The event catalogue grows as the platform grows. Instead of a fixed list that goes stale, query the current event types through the API:

• GET /propertymanagement/v2/query/webhooks.eventTypes — the up-to-date list of event types, machine-readable.

Webhooks cover create, update, and delete events across the core entity types, including objects, units, and contacts.

Setup

Webhooks are configured per tenant, either in the etg24 app or through the API:

• POST /propertymanagement/v2/command/webhooks.create — create a webhook with a name, URL, and the events to subscribe to.
• List, show, and delete your webhooks via the other endpoints in the Property Management v2 reference.

Each webhook can carry an authorization header that is sent with every delivery — so your endpoint can verify that the request comes from your webhook.

Delivery

When a subscribed event occurs, the event payload is forwarded directly to your webhook endpoint:

• Events are delivered as JSON POST requests to your configured URL.
• The payload contains the event data for the changed entity.
• Your authorization header, if configured, is attached to every delivery.

Typical patterns

• Two-way syncs — push contact changes into your CRM the moment they happen.
• Unit availability — update your listing system when a unit is created, changed or deleted.
• Watchdog automations — alert your team on object changes without polling the API.

Webhooks pair naturally with CQRS: events are the notification layer, commands and queries remain your action layer.