Connect Bookingengine with API - Revision history

Annette at 10:31, 23 October 2024

2024-10-23T10:31:41Z

← Older revision		Revision as of 10:31, 23 October 2024
Line 1:		Line 1:
	[[Category:~~API~~]]		[[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''

Annette at 22:04, 8 January 2024

2024-01-08T22:04:14Z

← Older revision		Revision as of 22:04, 8 January 2024
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

	~~Rates~~ can be read with JSON getRates		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.

Markkinchin: /* Price and Availability on demand */

2021-08-30T15:05:21Z

Price and Availability on demand

← Older revision		Revision as of 15:05, 30 August 2021
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 ==

Markkinchin: /* Price and Availability on demand */

2021-08-30T15:04:26Z

Price and Availability on demand

← Older revision		Revision as of 15:04, 30 August 2021
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.

	== Bookings ==		== Bookings ==

Markkinchin: /* Price and Availability for caching on your server */

2021-08-30T15:03:08Z

Price and Availability for caching on your server

← Older revision		Revision as of 15:03, 30 August 2021
Line 28:		Line 28:
	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.		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.

	~~If the property has a simple pricing structure using daily~~ prices~~, these~~ can be read with JSON getRoomDates		Daily prices can be read with JSON getRoomDates and their setup with JSON getDailyPriceSetup

			Rates 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 ==		== Price and Availability on demand ==

Markkinchin: /* Introduction */

2021-08-30T14:58:14Z

Introduction

← Older revision		Revision as of 14:58, 30 August 2021
Line 17:		Line 17:
	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.		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.		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.		2) The ability to save the resulting booking into Beds24 to adjust availability at all other channels.

Markkinchin: /* Introduction */

2019-10-19T16:10:23Z

Introduction

← Older revision		Revision as of 16:10, 19 October 2019
Line 6:		Line 6:

	== Introduction ==		== Introduction ==

			The Beds24 API is available at https://api.beds24.com

	Connecting a booking engine to Beds24 requires two functions.		Connecting a booking engine to Beds24 requires two functions.
Line 18:		Line 20:

	2) The ability to save the resulting booking into Beds24 to adjust availability at all other channels.		2) The ability to save the resulting booking into Beds24 to adjust availability at all other channels.




	== Price and Availability for caching on your server ==		== Price and Availability for caching on your server ==

Markkinchin at 16:07, 19 October 2019

2019-10-19T16:07:17Z

← Older revision		Revision as of 16:07, 19 October 2019
Line 19:		Line 19:
	2) The ability to save the resulting booking into Beds24 to adjust availability at all other channels.		2) The ability to save the resulting booking into Beds24 to adjust availability at all other channels.

	~~== API setup ==~~

Markkinchin at 16:06, 19 October 2019

2019-10-19T16:06:58Z

← Older revision		Revision as of 16:06, 19 October 2019
Line 9:		Line 9:
	Connecting a booking engine to Beds24 requires two functions.		Connecting a booking engine to Beds24 requires two functions.

	1) The ability to read price and availability from Beds24 for a particular booking condition		1) The ability to read price and availability from Beds24 for a particular booking condition.

	~~2) The ability to save the resulting booking into Beds24 to adjust~~ availability ~~at all other channels~~		There are two strategies for reading price and availability, either or both can be used depending on your needs.

	~~== API setup ==~~		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.

			2) The ability to save the resulting booking into Beds24 to adjust availability at all other channels.

	== ~~Create Properties~~ ==		== API setup ==


	~~== Setup Price and Channel Mapping ==~~

			== Price and Availability for caching on your server ==


	~~== Send Price~~ and ~~Availability ==~~		Availability is easy to read a year at a time with JSON getRoomDates, this can be stored and used to create availability calendars etc. on demand.

			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.

			If the property has a simple pricing structure using daily prices, these can be read with JSON getRoomDates

	~~== Bookings ==~~

			== Price and Availability on demand ==

			There are two functions which can return an exact price and availability for a known booking condition.

			OTA HotelAvail or JSON getAvailabilities, either of these can be used for a live request.

	~~== Booking Notification ==~~		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.



			== Bookings ==
	== ~~Booking Detail~~ ==


			Once a booking has completed on your booking engine, you can use either OTA HotelRes or JSON setBooking to enter the booking into Beds24.

	~~== Booking Modification ==~~		This will automatically reduce the availability accordingly at all other booking channels.

Markkinchin: /* Introduction */

2019-10-19T15:53:25Z

Introduction

← Older revision		Revision as of 15:53, 19 October 2019
Line 7:		Line 7:
	== Introduction ==		== Introduction ==

			Connecting a booking engine to Beds24 requires two functions.

			1) The ability to read price and availability from Beds24 for a particular booking condition

			2) The ability to save the resulting booking into Beds24 to adjust availability at all other channels

	== API setup ==		== API setup ==