Enquiries Channel manager Bookings Your website Booking engine Pricing Log in Sign up
v2026-09

Changelog

What has changed in the Brand Integration API, and what we consider ourselves free to change without telling you first.

Compatibility policy

The API version is stamped on every webhook as version and returned by GET /me. It is currently 2026-09.

Within a version, changes are additive only. Concretely, these may happen without notice:

  • A new field appears in a response or an event payload.
  • A new event type appears — you will only receive it if your subscription includes it.
  • A new optional request field is accepted.
  • A new error code appears for a case that previously had a more general one.
  • An error message is reworded. Branch on code, not prose.

These will not happen inside a version:

  • A field is removed, renamed, or changes type.
  • An existing field changes meaning.
  • A previously optional request field becomes required.
  • An endpoint changes path or method.

Parse defensively

Ignore fields you do not recognise, and never assert on the exact set of keys in a payload. A strict schema that rejects unknown properties will break on an additive change that every other integration absorbs silently.

A breaking change means a new version. Versions run in parallel, and we would agree a migration window with you before anything is switched off.

Releases

Every release below is version 2026-09, oldest first. The date on each is the day the change was merged; the live API has carried it from that day or shortly after.

Breaking changes since the initial release: none. No field, endpoint or error code has been removed or renamed in a response, and no request that worked before is refused now. One request field, property_category on property writes, is no longer read (12 November); a request that still sends it succeeds. Two releases, on 16 October and 12 November, changed what Doorloom does with data you already send; each such change is marked behaviour change or bug fix below, with what to check on your side.

24 September 2026 – Initial Public Release

The first public release.

  • Signed webhooks for availability, rates, restrictions, inventory, properties and bookings, plus a connectivity ping. Gap-free per-integration sequencing, full-state payloads, strict in-order delivery.
  • Property API: create with mandatory idempotency, merge-style update, and bulk create and update of up to 25 properties per call.
  • Booking API: create with mandatory idempotency, retrieve by either id, update with optional If-Match concurrency, and idempotent cancel.
  • Reconciliation: property listing, availability, rate and restriction snapshots sharing the webhook payload shapes, event replay over a 30-day window, and full re-sync.
  • HMAC-SHA256 request signing with a 24-hour dual-secret rotation window.

The three tables that follow list what differs from the preview documentation shared with partners between 3 and 24 September 2026. If you built against the preview, check them; if you started on or after the release, they simply describe the API as it launched.

New since the preview

Field Type Description
POST /properties new feature Create a property under your brand from your own system — name, type, description, address, room counts, occupancy, opening weekday/weekend rates, up to 50 units with your unit ids, and house-rule flags. Requires Idempotency-Key. The 201 is the GET /properties block. See Create a property.
PUT /properties/{id} new feature Merge-style update of a covered property, addressed by Doorloom id or your external id: listing facts, address, base rates, units by inventory_id or alias (an unknown alias creates the unit), and re-mapping or clearing your external_id. No idempotency key, no If-Match. See Update a property.
POST /properties/bulk, PUT /properties/bulk new feature Up to 25 properties per call. The batch is validated as a whole, then each item is written on its own and reported in results[] with a summary. Bulk create requires Idempotency-Key. See Bulk create and update.
external_id and external_unit_id are yours to set new feature Previously only Doorloom staff mapped them. You set them on create, and set, change or clear them on update. Uniqueness is per integration.
Coverage on create new feature A property you create is covered by your integration in the same transaction — coverage reads active in the 201 — listed by GET /properties and bookable immediately, regardless of your auto-enrol setting.
Initial snapshot on create new feature A created property sends property.changed, inventory.changed and the windowed availability.changed, rates.changed and restrictions.changed events across your horizon — the same set POST /sync produces for one property — within seconds.
property.changed on address and occupancy edits API change An in-place change to a property's address or occupancy — by the host or by you — now emits property.changed. Previously only renames, archiving and coverage changes did.
PROPERTY_EXTERNAL_ID_EXISTS API change 409 when an external_id you send is already mapped to another of your properties; errors.doorloom_id names it. On a create nothing is created; on an update the mapping is unchanged.
IDEMPOTENCY_KEY_REQUIRED on property creates API change The same 422 booking create returns, with a message naming the endpoint. Keys are one namespace per integration across every create.
New VALIDATION_FAILED keys API change units.N.external_id, units.N.inventory_id, units.N.name, units.N.is_active, units.N and properties.N.* — see the error reference.

Changed since the preview

Field Type Description
POST /sync is limited to one per 24 hours behaviour change The interval between full re-syncs was 10 minutes and is now 24 hours; the edge cap moved from six an hour to six a day. Nothing about the response shape changed — a too-soon call is still 429 SYNC_TOO_SOON with errors.retry_after, which now simply reports a much larger number. If you were re-syncing to recover from missed events, move to GET /events, which has no interval.
401 returns the standard envelope bug fix An unauthenticated call now answers an envelope whose code is UNAUTHENTICATED, instead of a bare message object. If you branched on the absence of code, branch on the status instead.
429 returns the standard envelope bug fix A rate-limited call now answers an envelope whose code is RATE_LIMITED, carrying errors.retry_after, instead of a bare message object. The Retry-After and X-RateLimit-* headers are unchanged.
Every endpoint has its own rate-limit tier behaviour change Reads, event replay, booking reads, booking writes, property writes and bulk property writes each have a dedicated per-minute budget under the unchanged 300-a-minute ceiling. See rate limits. If you were pacing only against the ceiling, the tightest tier that now binds is 120 property reads a minute.
The API is live in every environment removed There is no longer a platform-level switch that answers 404 for the whole API. An integration that Doorloom staff disable still gets 403 INTEGRATION_DISABLED; a paused one keeps API access and only stops receiving webhooks.

The 401 and 429 rows were documented as enveloped before they were. They now match the documentation, which means every failure from this API carries a code you can branch on.

Clarified since the preview, with no change in behaviour

Field Type Description
property.changed carries property_type documentation It was always sent, and was missing from the catalogue.
units[] carries code, is_default, max_occupancy, deleted documentation All four were always sent. deleted in particular is how you know to retire an alias.
Accept and X-Doorloom-Integration delivery headers documentation Both were always sent and were missing from the header list.
errors.availability.window.to is check_out minus one day documentation It is the last night of the stay, not the departure date.
Money is a JSON number documentation 13000.00 serialises as 13000. Parse numerically.
Timestamps are ISO-8601 with an offset documentation They carry an explicit offset, not a Z. Parse the offset. (The preview named the wrong zone; see the corrections of 12 November 2026.)
source.channel is not patchable documentation Only source.reference can be changed after create.
No acknowledge endpoint, no single-event resend documentation The after_sequence cursor is the only catch-up mechanism; a redelivery is always a new event.

28 September 2026

Field Type Description
property_rules.advance_booking_hours API change A new field on restrictions.changed and on GET /properties/{id}/restrictions: the host's minimum notice in hours (1 to 24, 48, 72 or 168), or null. When it is set it replaces advance_booking_days and same_day_cutoff_time as the advance-notice rule. Additive: the two older fields are still sent.

12 October 2026

Field Type Description
address.google_maps_url on properties new feature An optional field on POST /properties, PUT /properties/{id} and both bulk calls: the property's Google Maps link, up to 2048 characters. Doorloom uses it to show the Google place card on the brand's property page. See Create a property.

16 October 2026

Field Type Description
Per-date min_nights is enforced on brand websites behaviour change The payload is unchanged. dates[].min_nights used to be advisory everywhere; Doorloom now enforces it at guest checkout on the brand's own website, where a stay must meet the highest minimum among its nights. It is still not applied to POST /bookings, and neither are the other stay rules: a booking you send is checked for availability only. If your channel should respect the host's minimum stay, apply it before you take the booking. Per-date max_nights remains advisory.

23 October 2026

Field Type Description
address.google_maps_url accepts an embed snippet improvement You can send the whole Embed a map snippet Google gives a host; only its link is stored. On an update, null or an empty string now removes the link and its place card, and leaving the key out keeps it.

26 October 2026

Field Type Description
pricing.currency accepts currencies other than INR API change On POST /bookings and PATCH /bookings/{id} the field accepted only INR; it now accepts any supported ISO 4217 code, in either case, and an unsupported code is a 422 on pricing.currency. Omitted on create still means INR; omitted on update keeps the stored code.
The booking object echoes the booking's own currency API change pricing.currency in every booking response and in booking.changed was a fixed INR and is now the currency of that booking. If you send only INR, nothing you read changes. Amounts are never converted in this API. rates.changed is unaffected: listing prices are always in INR.

12 November 2026

Field Type Description
billing on bookings new feature Create and update accept billing.gstin, billing.company_name and billing.address for a business guest; they appear as the buyer on the GST invoice. The booking object echoes them as billing. An invalid GSTIN is a 422 on billing.gstin. On an update, a key you leave out keeps its value and null clears it.
guest.email and pricing.gst on the booking object API change guest.email is the stored guest email, and a PATCH that sends guest.email now replaces it; pricing.gst is {mode, amount}, the GST fixed for the booking. Both are additive.
payment.status paid means paid in full API change With no amount_collected, the whole total is recorded as collected. partial or unpaid with no amount records nothing.
Collected money is a payment, so pricing.balance is right bug fix payment.amount_collected was stored only as the advance, and pricing.balance (total minus payments) still showed the whole total as owed. It is now recorded as a payment on the booking, so balance is total minus what was collected, which is what this documentation always said. A later PATCH updates the same payment; 0 removes it. Check: if you worked around the old figure by computing the balance yourself, read pricing.balance again.
property_category is no longer read on property writes behaviour change Every property created through POST /properties or POST /properties/bulk is now listed as a vacation rental, whatever its property_type. property_category is no longer part of the request body: on a create or an update a value you send is ignored, the request still succeeds, and an update never changes the category a property already has. property_type is unaffected. If you send the field you can stop; if you relied on resort_hotel being stored, ask Doorloom to set it.
pricing.includes_gst fixes the booking's GST behaviour change It used to be stored and otherwise ignored, so the invoice worked GST out from the host's current settings and could add GST on top of a total you had already charged. Now true or omitted means total includes GST (split out on the invoice) and false means no GST; total is never changed, and a booking in a currency other than INR carries no GST. Applies to bookings created or re-priced from this release on. Check: that you send false for a booking on which no GST should appear. See GST.

13 November 2026

Field Type Description
PUT /properties/{property}/availability new feature Block or open nights and cap the units on sale, by date range, for the whole property or one unit. A block closes the night on the host's website and on the connected OTAs. Booked nights are left alone and reported in conflicts. See Update availability, rates and restrictions.
PUT /properties/{property}/rates new feature Set or remove the per-date nightly price, by date range.
PUT /properties/{property}/restrictions new feature Set or remove the per-date minimum and maximum stay, by date range.
Calendar writes: 10 calls per property per hour new feature Each of the three endpoints accepts 10 calls per property per hour, and a call carries up to 50 date ranges. Send ranges, not one call per date. See Limits.
Availability, prices and stay rules are no longer read-only documentation The overview said not to write them back. You now can; the host can still change the same nights, the last write wins, and every change reaches you as an event.

Documentation corrections, 12 November 2026

An audit of this documentation against the live API. Nothing below changed behaviour; each row is a place where the documentation said something the API did not do.

Field Type Description
Timestamps are in UTC documentation This documentation said timestamps were in Asia/Kolkata with a +05:30 offset, and its examples showed that. The API has always sent UTC, with +00:00. If you parse the offset, nothing changes for you. If you assumed +05:30, your stored times are five and a half hours out. Send updated_since in UTC as well.
pricing.partner_breakdown is your whole pricing object documentation It was described as the pricing.breakdown you sent. It is the full object (total, currency, includes_gst, breakdown), with later PATCH values merged in. Your own breakdown is at pricing.partner_breakdown.breakdown.
Creating a booking sends no booking.changed documentation The create page said a create is echoed back as an event. It is not: the 201 is the confirmation, and booking.changed begins with the first change after it.
Which changes send booking.changed and move revision documentation Dates, status, total, amount collected, guest counts, allocated unit, guest name and mobile. A change to only the billing details, guest email, note, currency or source reference sends no event, and a host edit of that kind does not move revision. See booking.changed and Staying in sync.
Stay rules are not applied to POST /bookings documentation The restrictions page said property rules are enforced at checkout without saying that this means the brand's website only. A booking sent through the API is checked for availability alone.
rates.changed currency is always INR documentation The field description suggested it could follow a booking's currency. Listing prices are in INR.
units[].meal_total is 0 on a booking you wrote documentation The meal plan you send is a label; its price is inside stay_price. The examples showed a non-zero meal total.
guest.email is returned, guest.country is not documentation The booking object page listed both as not returned.
Retries span about 14 hours documentation Twelve attempts on the published ladder take about 14 hours from first to last, not 12.
A 3xx final answer dead-letters the event documentation It was missing from the status table. Register the final URL rather than redirecting.
The response deadline is set by Doorloom documentation The limits page called it configurable per integration. It is, by Doorloom on request, between 1 and 30 seconds.
If-Match takes the bare revision number documentation With or without quotes. Any other value is ignored and the write proceeds.
Snapshots still answer for an inactive property documentation Availability, rates and restrictions remain readable after coverage is switched to inactive; only a property never mapped to you is a 404.
A second PROPERTY_ARCHIVED message documentation A booking create can also answer with the property's name in the message. Branch on code.
There is no off switch, and a 404 without a code is a routing miss documentation Two pages said a bare 404 on every route meant the API was switched off. No such switch exists. A 404, 405 or 500 that never reached an endpoint carries only a message.
Which 409 IN_PROGRESS to retry with the same key documentation Only the one whose message says the key is still being processed. The one that says the external id is being created is stored against the key; retry it with a new key. See Errors.
A removed property sends no property.changed documentation coverage: inactive was described as an event you receive. It is visible only on GET /properties.
PUT /properties/{id} does not always send property.changed documentation Only a change to the name, type, address or occupancy does.
A dead-lettered event is recorded, not escalated documentation Pages said Doorloom staff are alerted. An incident is recorded for staff; the event is not sent again and does not count towards the automatic pause. A handler with the wrong secret therefore rejects every event.
Smaller corrections documentation Weekday prices cover Sunday to Thursday nights. property_type values are lower case (villa, home_stay). POST /sync echoes types as you sent them. Probes run for automatic and 410 pauses only. GET /events returns the same values as the webhook but not the same bytes. The API key is a number, a bar and a long random string, and all of it is sent. Listing prices are always in INR.

Staying informed

Doorloom contacts integration partners directly about anything that affects them. If the right person for that is not the person who set up your integration, tell [email protected] who it should be.

Something unclear or wrong on this page? Write to [email protected] and tell us which page — we would rather fix the doc than answer the ticket twice.