Event catalogue

Seven event types. Six describe the brand's inventory and bookings; the seventh is a connectivity check.

Type	Scope	Carries
`availability.changed`	property + date window	How many units are sellable on each night of a date window.
`rates.changed`	property + date window	The nightly price for each night of a date window, plus the extras that sit on top of it.
`restrictions.changed`	property + date window	Stay rules, both the property-wide ones and the per-night ones.
`inventory.changed`	property	The full unit list for a property, including units that are no longer sellable.
`property.changed`	property	The identity and status of one property.
`booking.changed`	property	The full current state of one booking.
`ping`	none	A connectivity check. Answer 2xx.

Choosing what you receive

By default you receive every type. Doorloom staff can narrow that to a subset for your integration; GET /me reports the current list as webhook.event_types.

ping is always delivered regardless of subscription, because it is how a paused endpoint is tested for recovery.

Which ones you actually need

Most integrations do not need all six. Pick by what your system does.

Reselling inventory — you need availability.changed, rates.changed and restrictions.changed. These are the three that change constantly.
Keeping a catalogue in step — add property.changed and inventory.changed. These are rare and small.
Writing bookings back — add booking.changed, so a host-side edit or cancellation reaches you.

What every event shares

The envelope is identical across all seven, and the apply-if-newer rule applies to all of them. Read those two pages before the individual payloads; the per-event pages below assume both.