17,129
edits
Changes
Jump to navigation
Jump to search
If the property has a simple pricing structure using daily Daily prices, these can be read with JSON getRoomDatesand their setup with JSON getDailyPriceSetup
no edit summary
1a) Price and availability can be read in advance and stored or cached on your server, this has the advantage that your server can respond quickly with it's local copy of the data.
1b) Price and availability can be read on demand in real time, this has the advantage of accuracy but may slow down your page. This option is not suitable for multiple properties or situations where many API calls will be needed.
2) The ability to save the resulting booking into Beds24 to adjust availability at all other channels.
Price is more difficult, especially when prices change based on occupancy or length of stay, in this case the exact price can only be shown once the stay dates and occupancy are known.
Fixed Prices can be read with JSON getRates
These should be read approximately once per hour and stored on your server. Your server can use the data to respond to searches quickly without requiring API calls.
Only once a selection of room type, dates and occupancy has been made, make a live call to JSON getAvailabilities to check the data is still current.
In the unlikely event that it has changed or the room has been sold, you can display a "Sorry this selection has just been booked" message and offer another search
== Price and Availability on demand ==
These functions are only suitable for looking up data for one particular booking condition in real time, they are not intended to read bulk data for caching.
Any strategy that requires more than a few API calls for a live request should use the caching strategy, otherwise you risk slow page times and possible failure due to API limiting.
== Bookings ==
