API availability endpoint applies property-level booking rules such as changeover days.
We want people to be able to search for availability and go through to book without needing to recreate functionality that already exists in your system. What we need to do is call the other property endpoints and store that info on our system (short lived), then when we want to populate the calendar for what is/isn't available we need to get all availability and then cross reference that list against the rules and remove dates that can't actually be booked.
That is a lot more work than just querying /api/v3.3/properties/UID/availability and displaying that to the user, and is also prone to error if we don't implement the rules exactly as you have them.
1
vote
Richard [not provided]
shared this idea