The Best Price widget can be added to a customer's website to display the best available lead price for a property within the next 30 days or another specified timeframe.  The price calculation is based on "real-time" availability from the SynXis CRS for specified stay criteria.

The Calendar widget can be used to display a live availability calendar with pricing and availability based on real-time data from the SynXis CRS.  It can be used as a static calendar view or as a date selector with a search link to the SynXis Booking Engine.

The Hotel Availability API returns detailed availability and pricing information for a single hotel.

The Hotel Content APIs provide several different ways to search for a list of hotels and to retrieve associated static descriptive content.

Returns a Lead Availability single price element over a date range or a Calendar Availability daily breakdown of price elements over the date range.

Returns a list of active hotel or chain level single and multi-use coupon configurations.

Returns a group information for a specified hotel.

Use these APIs to retrieve a list of Rooms, Rates, Rate Categories, Rate Filters or Products from SynXis CR. The results can include all items for the category or narrowed down using filter criteria.

Use this API to retrieve a list of promotions configured at a chain or hotel level.

These APIs provide orchestrations relating to creating, modifying, canceling, retrieving, and back-office processing of hotel reservations.

Utility services that support creating, modifying, canceling, retrieving, and back office processing of hotel reservations.

The Search Bar Widget can be used to display a fully functional search bar including a hotel list, live availability calendar, occupancy selection, special codes and rates, rate filters, and/or submit (redirect) functionality. 

Using Single Sign On (SSO), you can redirect a signed in members from a CRM member portal to the SynXis Booking Engine while retaining the signed in state. Consequently, member-only products are immediately available for selection. Usage Notes: 1. The CRM must send the access_token value from the API response to the client (browser) as part of transitioning the user to SBE. It is the presence of this token that controls whether the user is treated as logged in to SBE or not. 2. The access_token value generated from this call must not be shared with other clients. 3.