API Change Log

Joel P
Feb 5, 2025 8:16 AM
OR Team Member Joined Oct, 2009 149 posts

Hello developer community! Welcome to the API Change Log. This topic is dedicated to important updates about the OwnerRez APIs. We recommend you watch this topic to be alerted about changes that may impact your applications.

Happy coding!

Joel P
Feb 5, 2025 8:16 AM
OR Team Member Joined Oct, 2009 149 posts

Hello developer community! Welcome to the API Change Log. This topic is dedicated to important updates about the OwnerRez APIs. We recommend you watch this topic to be alerted about changes that may impact your applications.

Happy coding!

Joel P
Feb 13, 2025 5:01 PM
OR Team Member Joined Oct, 2009 149 posts

Breaking Change: Required Field "currency" on SpotRates

[This change was announced on January 6, 2025 and goes into effect on March 1, 2025]

The PATCH v2/spotrates endpoint now requires currency to be explicitly specified for each rate. With this update, every rate entry must include a 3-character currency specification.

Example:

{
    "property_id": 123,
    "date": "yyyy-mm-dd",
    "amount": 123.00,
    "currency": "USD"
}

This change ensures the currency provided matches the property's configured currency. The purpose of this change is to avoid mis-pricing issues caused by differences in configuration between the rate supplier and OwnerRez. 

You may begin sending requests containing currency immediately, but validation will only be enforced starting on March 1.

From March 1, any patch requests to SpotRates that do not include a currency value will result in an error. Additionally, any patch requests that contain a currency value different from the property's configured currency in OwnerRez will result in an error.

Joel P
Feb 14, 2025 9:49 AM
OR Team Member Joined Oct, 2009 149 posts

Breaking Change: v1.1 Quotes Arrival and Departure dates should not include time values

[Change effective February 12, 2025]

This is a validation change to the legacy v1.1 API. Prior to this change, if a user submitted a Quote value to v1/quotes containing Arrival and Departure dates that also included timestamps, we would not error but would attempt to store those time values. This caused problems downstream because Arrival and Departure are only intended to be timeless dates.

We have modified the PUT, POST, and TEST verbs on v1/quotes to validate that Arrival and Departure parameters do not include a timestamp. If a timestamp is included, a 400 error will be returned.