Connect Bookingengine with API: Difference between revisions
Jump to navigation
Jump to search
Markkinchin (talk | contribs) |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category: | [[Category:API_V1_deprecated]] | ||
''This page explains how to connect a Booking Enging to the Beds24 API for Channel Management'' | ''This page explains how to connect a Booking Enging to the Beds24 API for Channel Management'' | ||
| Line 30: | Line 30: | ||
Daily prices can be read with JSON getRoomDates and their setup with JSON getDailyPriceSetup | Daily prices can be read with JSON getRoomDates and their setup with JSON getDailyPriceSetup | ||
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. | 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. | ||
| Line 46: | Line 46: | ||
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. | 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. | 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 == | == Bookings == | ||