Overview
Connect your own system — a PMS, a channel manager, or the website you already run — to a brand on Doorloom. Doorloom pushes calendar and pricing changes to you as signed webhooks; you push bookings back over a REST API.
Only want to link to a booking page?
Then you need none of this. A brand’s guest booking page takes its whole state from the query string, so a link can arrive with the dates, properties, guests and meal plans already chosen — no credentials, no integration. See booking page links.
The rest of this portal is the Brand Integration API. It has two halves, and most integrations need both.
- Doorloom → you: webhooks Availability, rates, restrictions, inventory, properties and bookings, signed and delivered in order. You never poll for calendar changes.
- You → Doorloom: REST API Create and update properties, one at a time or in bulk. Create, update, cancel and read bookings. Pull snapshots and replay missed events when you need to reconcile.
Who owns what
Doorloom is the source of truth for inventory and pricing. Availability,
prices and stay rules are set by the host in Doorloom, and reach you as events. Do not write
them back. The one exception is a property you create through the API: you give it its opening
base rates and its units, and may correct those base rates with PUT — after which the
calendar, custom prices and rules are the host's, and yours to read.
Listing facts are shared. A property's name, type, address, occupancy and
unit list can be changed by the host in the app or by you through the API; either way every
covering integration hears about it as property.changed.
Your system is the source of truth for the bookings it makes. You set the price on a booking you create; Doorloom stores your total and does not re-price it. Once the booking exists, either side can change it, and every change is announced to the other.
One property per booking
Base URL and version
https://doorloom.com/api/integrations/v1The API version is 2026-09. It is stamped on every webhook as
version and returned by GET /me.
Within a version, changes are additive only: new fields may appear, existing
fields will not change meaning or disappear. Parse defensively and ignore what you do not
recognise. A breaking change means a new version, negotiated with you first.
Getting access
Integrations are not self-service. Doorloom staff create yours against a specific brand and hand you an API key and a webhook secret once. Write to [email protected] to start that conversation.
Which properties you cover is then up to you and the brand: every property you create through
POST /properties is
covered at once, properties the host creates in the Doorloom app join automatically when your
integration auto-enrols, and staff can add or remove any of the brand's properties by hand.
Coverage is always properties the brand owner owns. Properties they merely
cohost for someone else are never included.
What to read next
If you are integrating end to end, read in this order. Each page assumes the ones before it.
- 1. Authentication Your two credentials and what rotating each one does.
- 2. Conventions The envelope, dates, money and timezones. Short, and it applies to every page after it.
- 3. Ordering and idempotency The one rule your webhook handler must implement.
- 4. Quickstart First call, first property, first verified webhook, first booking — the full onboarding sequence.
A note on what this API is not
This is not the API the Doorloom mobile and web apps use. That one is internal, unversioned and changes without notice. Everything documented here is a contract we hold still.