Subject
Action Needed: Breaking Change to CreateBooking!
Body
Hi [first name]!
On Dec 1, OwnerRez is launching a new endpoint for New Booking requests. This endpoint goes live on Dec 1, and the old endpoint will be deactivated on Jan 1. The new endpoint is now active in Stage for testing.
What is going to change
Send new-booking requests (/haxml/haolb/createbooking) to vault.ownerrez.com instead of fast.ownerrez.com:
E.g.: https://vault.ownerrez.com/haapi/haolb/createbooking?type={your type}&key={your key
(The stage path is the same. Use vaultstage.ownerrez.com as the host name to test in stage.)
Keep everything else about the request the same:
- the request body
- the query string
- the Basic authentication credentials
- the XML content type you send today
Requirements
- Send a Content-Length header; the new endpoint refuses chunked requests without one.
- If you send cardholder data to OwnerRez, continue to do so in the paymentCard/number and paymentCard/cvv where you do today. Also keep sending maskedNumber and paymentCardDescriptor/cardCode.
Timing
Nov 16: vaultstage.ownerrez.com is live for testing and verification
Dec 1: vault.ownerrez.com goes live in production
Jan 1: fast.ownerrez.com/haxml/haolb/createbooking will stop accepting requests (the stage version will also stop on this date)
What is not going to change
Keep all other traffic on fast.ownerrez.com, including listings, content, availability, rates and quotes. Please don't move those calls to the new domain. If your configuration uses one base URL for everything, override only the booking endpoint.
Please contact partnerhelp@ownerrez.com if you have any questions!
The OwnerRez Team