Redeam Booking API Overview
We put together this Quick Start page to give a summary of the different parts of the Redeam Booking API with links to the corresponding API documentation. The requests and responses use a versioning scheme and a simple customer headers authentication scheme which needs to be included. The necessary authentication keys will be provided to you as part of the on-boarding process.
Suppliers
The Redeam Booking API allows you integrate with Suppliers connected to Redeam and get access to their supplier information. You can get a list of available Suppliers to find out more about their location, hours of operation and accepted traveler types or alternatively, by providing a Supplier ID for a particular Supplier, you can get only their details. Redeam highly recommends to implement and use the Supplier ID capability. Find the API calls here: Retrieve Suppliers
Products
Suppliers provide all their bookable products via the Redeam Booking API and add a product description, location, hours of operation and traveller types. If you have a specific Product ID, the details of only this product displays. Find the API calls here: Retrieve Products
Rates & Price Schedule
In order to get up to date prices a combination of the Rates and Price Schedule APIs need to be implemented and used. This combination guarantees that static rates as well as dynamic rates can be consumed and supported to be booked via the Redeam Booking API. Find the API calls here: Retrieve Rates and Fetch Price Schedule
Availability
The Booking API provides real-time product availability checks. Sending an availability request with a Supplier ID returns remaining capacity and availability start and end times for all available products. By specifying the Product ID, the same details for a specific product return. Find the API calls here: Retrieve Availability
Holds
In the Redeam Booking API it is mandatory to implement a Hold, but not always mandatory to send a Hold before a booking is created. The issued Hold ID is required to retrieve and release the Hold, however, these two calls are optional. Find the API calls here: Manage Holds
Bookings & Cancellations
Creating a booking requires a Hold ID and references to attributes in availability, product and pricing API calls which is outlined in more details in the API. If a Booking needs to be retrieved and cancelled, the Booking ID is required to locate it. Find the API calls here: Manage Bookings
Extension Maps
Throughout all the transaction types you will find Extension Maps. These fields allow the Reseller, Redeam and / or the Supplier to exchange additional information that does not fit within a previously defined field. These fields are very helpful and sometimes required depending on the Supplier you are connecting to so please implement the consumption of these fields. Additional information can be found here: Extension Maps