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

Update availability, rates and restrictions

Block or open nights, set a per-date price, and set a per-date minimum or maximum stay, for a property you cover and a list of date ranges. Doorloom applies the change to the host's calendar and pushes it to the OTAs the host has connected. Each call answers with the current snapshot for the dates it touched.

Three endpoints, one request shape. They are the write side of the snapshot endpoints at the same paths.

PUT https://doorloom.com/api/integrations/v1/properties/{property}/availability
PUT https://doorloom.com/api/integrations/v1/properties/{property}/rates
PUT https://doorloom.com/api/integrations/v1/properties/{property}/restrictions

{property} is the Doorloom id or your external_id; Doorloom resolves whichever it recognises. The property must be in your active coverage — one that Doorloom staff removed from your integration is a 404, and an archived one is 422 PROPERTY_ARCHIVED.

10 calls per property per hour: send ranges, not one call per date

Each of the three endpoints accepts 10 calls per property per hour. One call carries up to 50 date ranges, so a whole season is a single request. A loop that sends one call per date is refused from the eleventh call with 429 RATE_LIMITED. See Limits.

Headers

Field Type Required Description
Authorization string Required Bearer <your API key>.
Content-Type string Required application/json.

No idempotency key

A PUT here sets state: sending the same body twice reaches the same calendar, so a retry is always safe. There is no revision counter. The host can change the same nights in the Doorloom app, and the last write wins, whether it came from you or from the host.

Request body

The body is a list of date ranges. Every range carries the fields of the endpoint you are calling, described in the sections below.

Body

Field Type Required Description
updates array Required 1 to 50 ranges.
updates[].from string Required YYYY-MM-DD. First night, inclusive. Today or later, in Asia/Kolkata.
updates[].to string Required YYYY-MM-DD. Last night, inclusive. On or after from, and at most 730 days ahead of today.
  • One request spans at most 92 days, from its earliest from to its latest to. Send a longer period as several requests.
  • Ranges in one request may not overlap. A night that appears twice is a 422 on the later range's from, so the result never depends on the order of the list.
  • A field you leave out is not changed. Where a field accepts null, null clears the stored value.
  • A single night is a range whose from and to are the same date.

Availability

Fields of each range on PUT /properties/{property}/availability

Field Type Required Description
updates[].is_blocked boolean one of the two true closes the night. false opens it.
updates[].units_cap integer|null one of the two The most units on sale that night, from 0 to the property's unit count. null removes the cap. Applies to the whole property, so it cannot be sent with unit.
updates[].note string|null Optional Up to 255 characters, shown to the host on the blocked night. Without one, the note is Blocked via followed by your integration's name.
updates[].unit object Optional Limit a block to one unit of the property. Omit it to address the whole property.
updates[].unit.inventory_id integer one of the two The unit by Doorloom's id.
updates[].unit.external_unit_id string one of the two The unit by your alias.

A block closes the night everywhere: the host's own website and booking page stop selling it, and Doorloom sends the connected OTAs zero availability and a stop-sell. In the snapshot the night reads is_blocked: true, available_units: 0 and block_scope: "everywhere". A block that closes the OTAs only cannot be set through the API.

Request bash
curl -X PUT https://doorloom.com/api/integrations/v1/properties/VILLA-9/availability \
  -H "Authorization: Bearer $DOORLOOM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "updates": [
      { "from": "2026-12-24", "to": "2026-12-26", "is_blocked": true, "note": "Owner stay" },
      { "from": "2026-12-27", "to": "2026-12-31", "units_cap": 1 }
    ]
  }'

Booked nights

A block never cancels or moves a booking. Nights that cannot be changed are left as they are and listed in conflicts; every other night in the request is written.

conflicts[].reason

Field Type Description
booked reason Every unit you addressed is booked that night. Nothing was written for it.
partially_booked reason A range for the whole property met a night on which some units are booked and some are free. Nothing was written for it. To close the free units, block them one by one with unit.
linked_listing reason You opened the night, but a linked listing still holds it: the host has set these listings to block each other, and the other one is booked or blocked.

When a booking is cancelled later, its nights open again unless they were blocked. A night reported as booked was not blocked, so block it again if you still need it closed. You will hear about the cancellation as an availability.changed event.

A reservation is a booking, not a block

When your system takes a reservation, send it with POST /bookings. The booking closes its nights by itself and the host sees the guest. Use a block for nights that are off sale for another reason: maintenance, an owner stay, a seasonal closure.

Units

A property with more than one unit is blocked either as a whole or unit by unit.

  • Without unit, the range applies to every unit of the property.
  • With unit, only that unit is closed or opened. The other units keep selling, and available_units for the night drops by one. When the last free unit is blocked the night reads is_blocked: true.
  • Opening one unit of a night on which the whole property was blocked opens that unit only; the other units stay closed.
  • Two ranges may share a night when they name different units. A range for the whole property overlaps every unit.
  • On a property with a single unit, unit changes nothing: the unit is the property.

Unit ids and aliases are the ones on GET /properties and inventory.changed. An alias Doorloom does not know, or a unit of another property, is 422 UNIT_NOT_MAPPED; a deactivated or deleted unit is 422 UNIT_INACTIVE.

The snapshot counts units; it does not name them

Availability is reported per property per night. After you block one unit you see available_units fall, but neither the snapshot nor the event says which unit is blocked. Keep that in your own system.

Response

The availability snapshot for the window your request covered, read after the write, plus conflicts.

Response 200 json
{
    "success": true,
    "message": "Availability updated",
    "data": {
        "sequence": 1047,
        "property": {
            "doorloom_id": 902,
            "external_id": "VILLA-9"
        },
        "window": {
            "from": "2026-12-24",
            "to": "2026-12-26"
        },
        "data": {
            "total_units": 2,
            "units": [
                "…"
            ],
            "dates": [
                {
                    "date": "2026-12-24",
                    "available_units": 0,
                    "total_units": 2,
                    "is_blocked": true,
                    "block_scope": "everywhere",
                    "units_cap": null
                },
                {
                    "date": "2026-12-25",
                    "available_units": 1,
                    "total_units": 2,
                    "is_blocked": false,
                    "block_scope": null,
                    "units_cap": null
                },
                {
                    "date": "2026-12-26",
                    "available_units": 0,
                    "total_units": 2,
                    "is_blocked": true,
                    "block_scope": "everywhere",
                    "units_cap": null
                }
            ]
        },
        "conflicts": [
            {
                "date": "2026-12-25",
                "reason": "partially_booked"
            }
        ]
    }
}
Field Type Description
sequence integer The sequence watermark, read before the snapshot was built. Use it as on a snapshot GET.
property object Which property this is, by both ids.
window object From the earliest from to the latest to in your request.
data object The availability payload, exactly as the snapshot and the availability.changed event carry it.
conflicts array Nights that were not changed, each {date, reason}, in date order. Empty when everything was written. Availability only.

Rates

Fields of each range on PUT /properties/{property}/rates

Field Type Required Description
updates[].base_price number|null Required The nightly price for that date, greater than 0. null removes the per-date price, and the night goes back to the property's weekday or weekend rate.
Request bash
curl -X PUT https://doorloom.com/api/integrations/v1/properties/VILLA-9/rates \
  -H "Authorization: Bearer $DOORLOOM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "updates": [
      { "from": "2026-12-24", "to": "2026-12-31", "base_price": 18500 },
      { "from": "2027-01-01", "to": "2027-01-05", "base_price": null }
    ]
  }'
  • The price is the same figure as dates[].base_price on the rates.changed payload: the room price for base_guests, in INR, before extra guests and meals. Whether it includes GST is the property's setting, price_includes_gst in the same payload.
  • A date you priced reads source: "custom". After null it reads base or override again.
  • There is one price per property per date, for every unit. A unit is a 422.
  • The price is written on every night in the range, booked nights included. A booking keeps the price it was made at.
  • The weekday and weekend rates themselves, and the extra-guest prices, are changed with PUT /properties/{id}.

The response is the rates snapshot for the window, with the message Rates updated. It has no conflicts.

Restrictions

Fields of each range on PUT /properties/{property}/restrictions

Field Type Required Description
updates[].min_nights integer|null one of the two The minimum stay for that date, 1 to 730. null removes the per-date value, and the property's rule applies again.
updates[].max_nights integer|null one of the two The maximum stay for that date, 1 to 730, and not less than min_nights when both are sent. null removes it.
Request bash
curl -X PUT https://doorloom.com/api/integrations/v1/properties/VILLA-9/restrictions \
  -H "Authorization: Bearer $DOORLOOM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "updates": [
      { "from": "2026-12-24", "to": "2027-01-01", "min_nights": 3 }
    ]
  }'
  • Send one key or both. The key you leave out keeps its stored value, so the example above does not touch max_nights.
  • stop_sell is not a field you set. It is derived from blocks: close a night with PUT /properties/{property}/availability. Sending it here is a 422.
  • Stay rules are per property per date, for every unit. A unit is a 422.
  • The property-wide rules in property_rules (the default minimum stay, advance notice, same-day cutoff) are the host's and cannot be changed through the API.
  • What each rule does once stored is on the restrictions.changed page. They are not applied to POST /bookings.

The response is the restrictions snapshot for the window, with the message Restrictions updated. It has no conflicts.

Limits

Field Type Description
Calls per property per hour integer 10 on each endpoint. Availability, rates and restrictions are counted separately, so a price update never uses up the calls you need to block a night.
Calls per minute integer 60 across the three endpoints and all your properties.
Ranges per call integer 50 entries in updates[].
Span of one call integer 92 days from the earliest from to the latest to.
Horizon integer 730 days ahead of today.

The hourly limit is counted per property, whichever id you address it by. A call that fails validation is not counted against it. The hour starts with the first counted call and the budget returns when it ends.

Response 429 json
{
    "success": false,
    "code": "RATE_LIMITED",
    "message": "This property's availability can be updated 10 times an hour. Retry after 1840 seconds, and send date ranges instead of one call per date.",
    "errors": {
        "retry_after": 1840
    }
}

The Retry-After header carries the same number of seconds. Nothing in a refused call is written. To change many dates, put them in one call: consecutive nights with the same value are one range, and up to 50 ranges fit in a request.

What happens afterwards

  • The host sees it. The nights change on the host's calendar in the Doorloom app, and the change is listed in the property's activity log under your integration's name.
  • The OTAs receive it. For a property connected to Doorloom's channel manager, the new availability, price or stay rule is sent on to the connected OTAs.
  • You receive it back. Your own write is delivered to your webhook as availability.changed, rates.changed or restrictions.changed, as full state for the window. A block sends both the availability and the restrictions event, because it also sets stop_sell. Apply them by the sequence rule like any other event.
  • The host can change it again. A host edit of the same nights replaces what you wrote and reaches you as an event. If your system must stay in step, apply the event rather than writing your value back.

Errors

Errors

Status Code Meaning
422 VALIDATION_FAILED The request body failed validation. errors is Laravel's field bag: an object keyed by field path, each holding an array of messages.
404 NOT_FOUND No such booking or property for this integration. Another integration's booking or property is not found rather than forbidden, so ids cannot be probed across partners. On a property write, a property whose coverage staff have removed is also not found.
422 PROPERTY_ARCHIVED The property exists and is covered, but the host has archived it. Archived properties are off-market: they cannot take bookings, and they cannot be edited through the API.
422 UNIT_NOT_MAPPED A booking's units[] line, or the unit of an availability write, names a unit alias Doorloom does not know, or one that belongs to a different property.
422 UNIT_INACTIVE The unit is mapped but no longer sellable — deactivated or deleted by the host.
409 IN_PROGRESS Two of your requests overlapped and this one lost. Either the same Idempotency-Key is still being processed, or another request is creating the same external id or changing the same property.
429 RATE_LIMITED You exceeded one of the rate limits. The standard Retry-After and X-RateLimit-* headers are set on the response. The second message is the calendar-write limit: 10 calls per property per hour on each of PUT availability, rates and restrictions.
401 UNAUTHENTICATED No API key, or a key that is not valid. Rotating your API key invalidates the previous one immediately.
403 NOT_INTEGRATION_TOKEN The bearer token is valid but is not an integration API key — it belongs to another Doorloom token surface. Integration keys are the only credential this API accepts.
403 INTEGRATION_DISABLED Doorloom staff disabled this integration. No events are recorded and no API call succeeds. This is distinct from paused: a paused integration keeps full API access and only stops receiving webhooks.

A validation error names the range by its position, for example updates.1.from or updates.0.units_cap. A request refused with a 422, a 404 or a 429 writes none of its ranges.

Retrying

A timeout, a 5xx or a 409 IN_PROGRESS can be resent unchanged: the write sets state, so repeating it is safe. Every call that passes validation counts towards the hourly limit, a repeat included. After a 429, wait Retry-After seconds. Any other 4xx means the body is wrong or the property is gone from your scope; fix the cause rather than retrying.

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.