API Bug Fixes

Hello developer community! Welcome to the API Bug Fix Log. This topic is dedicated to documenting bug fixes for the OwnerRez APIs. You may watch this topic if you are interested in being alerted about fixes that may impact your applications.

Happy coding!

Patch 250212

• GET v2/properties?include_fields=true
  Bug: An error was returned if any property in the result set had a total length of custom field values exceeding 16kb.
  Fix: We've increased the maximum to 256kb.

Patch 250416

• GET v2/property/{id}
  Bug: Incorrect Booking.com Room ID included in response body.

Patch 250521

• GET v2/messages?thread_id={threadId}&since_utc={since_utc}&sinceUtc={sinceUtc}
  Bug: Airbnb request-to-book (RTB) threads did not include the related quote ID.

Patch 250528

• GET v2/bookings/{id}
  Bug: Some bookings with related door codes were causing HTTP 5xx errors.

Patch 20250819

• GET v2/bookings/{id}
  Bug: Currency code was not always populated on bookings fetched singly by Id.
  Fix: We will now populate Currency code from the property or user configuration if not specified explicitly on the booking.

Patch 260513

• GET v2/payments/{id} and GET v2/refunds/{id}
  Bug: Both return is_deposited: false for payments/refunds that were marked deposited via the Deposits → Batch Update tool (or any "Mark as Deposited Elsewhere" path)
  Fix: Both now return the correct deposit status for transactions marked deposited elsewhere.

Patch 261014

Calendar date filters on v2 and v1 endpoints

• v2: GET v2/guests and GET v2/bookings from/to; GET v2/calendar, GET v2/calendar/{property_id}, and GET v2/spotrates from/to; GET v2/propertysearch available_from/available_to; GET v2/properties availability_*
• v1: bookings and listings availability, listings pricing, properties GET/lookup/search/searchandquote, and quotes expiresNotUtc

Bug: A date sent with a time or UTC offset was converted to UTC before it was compared with stay dates, which could shift it to another day. GET v2/guests?from=2026-03-01T00:00:00-05:00 filtered from March 1 at 05:00 and left out a guest departing March 1. to=2026-03-01T00:00:00+14:00 became February 28 and left out a guest arriving March 1. A time with no offset, such as 2026-03-01T12:00:00, also left out boundary stays.

Fix: These parameters now use the calendar date as written and ignore any time or offset. 2026-03-01, 2026-03-01T12:00:00, 2026-03-01T00:00:00-05:00, and 2026-03-01T00:00:00+14:00 all filter on March 1 in the property's time zone. Numeric dates are read month-first (03/01/2026 is March 1). A value that is not a date returns 400: '{value}' is not a valid value for '{param}'; expected a date/time.

Timestamp parameters such as since_utc and created_since_utc are unchanged and still convert to UTC.

Patch 261012

Booking.com reservations in GET v2/bookings and webhooks

Bug: New, changed, and canceled Booking.com reservations, and the holds created for them, were saved without committing. GET v2/bookings sent with the last ETag returned 304 Not Modified until another booking change on the account. Webhooks reported a new Booking.com booking only as entity_update. Linked properties stayed open for those dates for up to 10 minutes.

Fix: Each Booking.com reservation now commits as soon as it is pulled. The bookings ETag changes right away, and linked properties are blocked right away.

Webhook changes:

• A new Booking.com booking now sends entity_create.
• Booking.com holds (blocks titled "Hold for <reservation id>:<room id>", is_block: true) now send entity_create, entity_update, and entity_delete webhooks. Filter on is_block or type to skip them.