Availability Exchange API Integration Process for OTA Partners

API Implementation Roadmap

The average timeline for an Availability Exchange integration spans approximately two months. In the initial month, the OTA Partner focuses on building matching endpoints, leading to certification by ResNexus. The subsequent month is dedicated to live testing, utilizing 3-5 ResNexus properties for Alpha testing.

Once a stable connection is established, the new OTA Partner becomes an accessible booking channel for all ResNexus properties.

The final phase may encompass the distribution of marketing materials, announcing the new connection between ResNexus and the certified OTA Partner.

Unisted on Availability Exchange

• ResNexus properties that have opted out of Availability Exchange.
• Properties can change this setting in ResNexus under Settings > Availability Exchange > Accepting Reservations.
  

Listed on Availability Exchange

• Properties are listed, but may or may not have provided ARI data for partners to use.
• ARI data may be available for individual units, but unit groups may not be configured. If ARI data is not available, the property must allow sharing that data in ResNexus under Settings > Availability Exchange.
• To receive reservations, properties must enable Direct Connect in ResNexus and add Availability Exchange as a channel.

Accepting Reservations on Availability Exchange

• Properties are ready to accept reservations from new partners immediately. Unit groups are preferred, if configured.