Retrieve bookings
Read one booking by Doorloom's id or your own, or page through all of them. Three endpoints, one representation.
All three return the
booking object, and all three see only
bookings that belong to your integration. Another integration's booking is a
404, not a 403, so ids cannot be probed across partners.
By Doorloom id
curl https://doorloom.com/api/integrations/v1/bookings/55231 \
-H "Authorization: Bearer $DOORLOOM_API_KEY"
The path segment must be numeric.
By your own id
curl https://doorloom.com/api/integrations/v1/bookings/external/PMS-100234 \
-H "Authorization: Bearer $DOORLOOM_API_KEY"
Useful when your system holds only its own reference — after a create whose response you lost, for instance. URL-encode the id if it contains anything exotic.
Listing
Query parameters
| Field | Type | Required | Description |
|---|---|---|---|
updated_since
|
string | Optional | A date or timestamp in UTC. Returns bookings changed since then. This is the polling parameter. An offset on the value is not applied, so convert to UTC before sending. |
status
|
string | Optional | One of pending, confirmed, cancelled, completed, refunded. |
property_id
|
integer | Optional | Doorloom property id. |
check_in_from
|
string | Optional | YYYY-MM-DD. Earliest check-in. |
check_in_to
|
string | Optional | YYYY-MM-DD. Latest check-in. |
page
|
integer | Optional | 1-based. Defaults to 1. |
per_page
|
integer | Optional | 1 to 200. Defaults to 50. |
Results are ordered by when they were last updated, oldest first. That
ordering is deliberate: a booking that changes while you are paging moves to the end of the list
rather than disappearing from it. Because the pages are numbered, such a move can shift one
booking across a page boundary, so finish a walk by calling again with
updated_since set to the highest updated_at you saw.
curl -G https://doorloom.com/api/integrations/v1/bookings \
-H "Authorization: Bearer $DOORLOOM_API_KEY" \
--data-urlencode "updated_since=2026-09-30T18:30:00+00:00" \
--data-urlencode "status=confirmed" \
--data-urlencode "per_page=100"
{
"success": true,
"message": "OK",
"data": [
{
"id": 55231,
"external_booking_id": "PMS-100234",
"revision": 2,
"status": "confirmed",
"…": "…"
},
{
"id": 55240,
"external_booking_id": "PMS-100241",
"revision": 1,
"status": "pending",
"…": "…"
}
],
"pagination": {
"page": 1,
"per_page": 100,
"total": 128,
"last_page": 2
}
}
pagination sits beside data, not inside it
data.pagination is
null.Polling versus webhooks
If you subscribe to
booking.changed,
you do not need to poll for the changes that event covers: dates, status, total, amount
collected, guest counts, allocated unit, guest name and mobile. A host edit to only the billing
details, the guest email or the note is not pushed and shows up here. A payment the host records
later changes pricing.balance without an event and without moving
updated_at, so read the booking by id when you need its current balance.
Poll with updated_since when you are recovering from an outage longer than the
30-day event retention, or as a slow belt-and-braces reconciliation. Store the highest
updated_at you have processed and pass it back next time.
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. |
| 401 | UNAUTHENTICATED |
No API key, or a key that is not valid. Rotating your API key invalidates the previous one immediately. |
| 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. |