COMMON QUESTIONS
ANSWERS TO OUR MOST COMMON QUESTIONS
Welcome to the FAQ page. Here, we've compiled answers to common questions about Availability Exchange, organized into clear sections for easy navigation. Whether you're a new user or need specific information, this resource is designed to provide quick and straightforward insights to our most common issues.
The bookings process includes two items. 1) Call the Quote endpoint to confirm rates and availability. 2) Call the CreateReservation to create the reservation.
Yes. We want OTA Partners to be able to specify the rates, offer promotions, or make rate adjustments for different classes of guest (eg. premium members). OTA Partners should only change rates within the bounds of contractual limits they have set with individual properties.
OTA Partners decide! If a property has not yet set up their property to receive reservations from Availability Exchange OTA Partners, they likely have not set up their unit groups either. OTA Partners can still connect to the property and start accessing their information by individual units, as that is automatically available. Once the property has unit groups set up, you can switch your API queries to using unit groups instead. Some properties have unique units though, so you'll want to support both versions.
We're working on this. We designed the endpoints to minimize the need for OTA Partner caching, but may expose timestamps to help with cache updates.
If OTA Partners are caching data, we recommend querying the next 30-90 days of availability and rates at least once per day as that is the most common lead time for most bookings. Otherwise, we designed the endpoints for partners to make queries on the fly. The quote and create reservation endpoints will always rely on the most up to date information.
Absolutely. All the properties in the sandbox are there for partners to test the reservation flow.
After leaving the sandbox, OTA Partners can continue making queries for sandbox properties, including making reservations. The only change is that the sandbox properties will no longer be listed under the GetBusinesses endpoint (unless a specific property is queried). We recommend saving the ID for at least one sample property so that your integration can continue to test reservation endpoints.
Shorten or extend a stay, change units, or reschedule a stay. To make these modifications, simply query the ModifyReservation endpoint with the desired state of the reservation.
Most often we are returning an error because the IP address the requests are coming from hasn't been added to the approved list.To fix this issue, send an email to info@availabilityexchange.com with the IP addresses you have approved for both sandbox & production.
Currently the API does not provide property level information and was designed to provide Availability, Rates, and Inventory (ARI) information at the unit level. The only property level information shared is the property name, address, and phone number. Partners should be prepared to collect and maintain property level information directly from the property managers if that information is necessary for your site.
A unit_group is a group of one or more units. Each unit in a unit_group has similar amenities and identical rates.
A unit is an individual room or site at a property and can exist in zero or one unit_group
If you send an AddReservation request using a unit_group_id it will add a reservation for one of the available units within that unit_group.
If you Send an AddReservation request using a unit_id it will add a reservation for that specific unit.
Each request should include only one unit_group_id or one unit_id
The GetQuote request will provide a quote for a specific itinerary, either for a unit_group or a unit depending on which id was provided.
All properties will have unit groups configured to share their inventory with your channel. The most common configuration is a one unit to a group configuration.
We currently don't provide an environment for partners to modify property and unit configurations. If you have something you would like to adjust on the test accounts, please reach out and we will adjust it for you.
When a ResNexus subscriber adds a channel they will automatically appear in the GetBusinesses call as a business. If for any reason they choose to disconnect and remove you as a channel, they will no longer appear in the GetBusinesses call and referencing the business id in other calls will no longer work.
The reservation message allows you to set your own price (quote.base_rate). The current room price is only used if the quote is not included, or the quote does not have the base_rate set.
We do not have a way to import listings into ResNexus. Each listing would need to be created by the hotel before linking it to the channel. In most cases, these listings are already configured, as this is completed with the ResNexus system setup.
Each time you call GetUnitGroups or GetUnits, you will receive the current description and image urls.
When you feel your development is complete and you have exercised the API, please request a meeting with your development contact to review your implementation and request certification. As long as there are no issues found with your implementation after reviewing reservations that have been made and canceled via the API, and you have provided the required logo and channel info page content, certification itself typically only takes a few days. Following certification, live test properties will be added in order to complete the trial period prior to the connection going live.
The business will appear in the GetBusinesses call immediately after the channel has been added in the back office.
There are a number of reasons why the Availability Exchange Gateway API (AE) would return a value other than the price shown in our booking engine. In general, the conflicts arise from AE having a simple occupancy based pricing system as opposed to the booking engine's itinerary based system. The most common specific causes for these differences are:
1. The property may choose to adjust the rates they are sending to OTA channels and partners.
2. The property has set up sliding rates.
Sliding rates adjust the price of an itinerary automatically based on a number of predefined criteria. Sliding rates are a ResNexus specific feature and we currently don't provide the adjustments to OTA channels or AE Partners. About 15% of our properties currently use sliding rates.
There are a few troubleshooting steps that may resolve your issue.
Verify the subscriber's business name in ResNexus matches the business you are looking for in your inventory
Have the subscriber log into ResNexus, navigate to settings>Direct Connect and verify your channel name is in their list of added channels.
Verify you are using good credentials and an approved IP address to make the call to the Availability Exchange API.
Verify you're using your live connection credentials for access and not using sandbox credentials.
Unit groups are the way users select what inventory is shared with you, the partner. The master unit in the group defines what rates, minimum nights, descriptions, and images are shared for that group, so only similar units should be grouped together. It is common to see groups configured with one unit per group.
To set up unit groups, direct the user to:
Sign into your ResNexus back office and navigate to the settings page
Select Direct Connect
Select on the channel name
Select Groups in the right hand menu
Select Create Group - Enter the group name, which will be shared with the OTA and may be used for display on their site.
Save the unit group. Repeat this process until all desired units are grouped.*
*Please note that there are many cases where the user will not want to share availability of all their units with your OTA
Verify you (the Partner) did not send over a rate override for the reservation.
Another common culprit for this issue is the user may have incorrectly configured their unit groups. Reservations made for a unit group will use the rate for that group, regardless of which unit is reserved. Have the user review their groups, looking for any units with rates varying from the rates of the master unit in the group. Direct the user to adjust their groups accordingly.
If this is not the issue, direct the subscriber to review their channel rate adjustments as well as look for any yield management rules in ResNexus. If these do not explain the discrepancy, we recommend directing them to the ResNexus Support team to review rate and group configurations to find the issue.
Unit groups with no availability will not be returned at all when querying for availability.
In most cases, an error was returned to your request to create the reservation, or the request did not go through as expected. Verify you got a response from Availability Exchange, and check for errors returned in that response. If you did not get any response, the request never made it to Availability Exchange.
ResNexus users are able to customize the information they share with partners. Among other settings, users can choose what inventory they want to share, what their rates will be on the partner site, and set different availability rules from their booking engine. Please note that the Availability Exchange API is the source of truth for your connection, and information should not be verified against the user's direct booking engine.
When requesting a unit or unit group's availability, any units that are not booked or blocked will be returned as available. However, when getting a quote or creating a reservation, there are additional factors that will be checked. This includes things such as minimum night requirements. The quote has the most complete and accurate information.
All Rights Reserved | Availability Exchange
Website Design & Reservation Software by ResNexus