AlpineBits FAQs

AlpineBits is not a stand-alone program or web application that you can install. It’s a communication protocol composed of a set of guidelines that enable different software systems to communicate with each other, specialised in the tourism and hospitality industry.
Video Link | List of kown implementations

AlpineBits is not a centralised database. It is a standard for exchanging tourism-related data (e.g., room availability, prices, bookings, etc.) where data is exchanged directly between partners.
List of known implemetations

Link to online documentation

In AlpineBits terminology, the “client” always initiates communication. In general, PMSs are clients, while web portals or channel managers are servers.

Handshaking enables automatic identification and negotiation of common functionality between partners wishing to communicate. This minimises human error and automatically updates functionality as partners update the protocol.

During Handshaking, partners exchange a message where they declare the protocol versions and functionalities they support.

No, mixing AlpineBits HotelData version is not allowed.

Exchanging request or booking messages can be done via GuestRequest. In the pull version, the message is requested by the client. In the push version, the message is sent by the server.

You can use the AlpineBits testing tool available at the following link: Link to testing tool

Carefully read the documentation to understand the protocol requirements.

• Implement a prototype of the system based on the protocol specifications.
• Validate messages according to AlpineBits and OTA XSD standards.
• Use testing tools to verify your implementation.
• Finally, request a certification for your implementation.
  Link to certification page

The requirements depend on the specific implementation. However, a stable and reliable connection is essential, particularly for servers waiting to handle client requests.

Documentation is available online and offline (PDF format). The offline package is a zip file that includes:

• A printable PDF version of the documentation
• A collection of XSDs for message validation
• All necessary sample files
• A trademark file

Link to AlpineBits HotelData page

No. The protocol is modular, so you only need to implement the messages relevant to your use case. However, Handshaking is mandatory.

Yes, event-related data can be exchanged using the DestinationData protocol. Learn more in the DestinationData documentation
For HotelData, only activities directly related to the accommodation facility are managed.

It is recommended to implement the latest version of the protocol. For compatibility with partners, you may also implement the previous version. However, while implementing older versions carefully read the Change Log of the most recent versions to be prepared for an easy upgrade path. The AlpineBits Alliance publishes a new HotelData release every two years. You can track updates in the version Change Log and in the public Git repositories.

To prepare for certification:

• Validate messages against the XSDs of the implemented protocol version.
• Follow the error-handling guidelines outlined in the documentation.
• Request the certification audit by following the outlined process.

Link to certification page

The certification process includes a comprehensive review to ensure that every statement in the documentation aligns with the messages produced by your implementation. While AlpineBits does not conduct detailed code reviews, it performs rigorous testing by exchanging messages with your implementation. The first step of the audit is validating these messages to ensure compliance.

The purpose of certification is to ensure that your implementation of the standard meets the defined technical requirements and operates as intended within the AlpineBits ecosystem.

The procedure is as follows:
Initial Consultation (Optional) A short introductory call can be arranged to discuss which parts of the AlpineBits standard are most relevant to your need:

• Implementation – Develop your AlpineBits implementation, focusing only on the functionalities essential to your product.
• Request for Certification – Once your implementation is complete, submit an official request to initiate the certification process.
• Certification Testing and Verification – AlpineBits conducts thorough testing to verify that your implementation complies with the standard and functions correctly.
• Certification Finalisation – After successful testing, certification is granted. You can then establish connections with the partners you wish to exchange data with.

Approx, 4-6 weeks however it depends on the correctness of your implementation.

Go to certification page

Yes, you can explore our curated list of known AlpineBits implementations, reflecting the best of our current knowledge.
Go to the list of known implementations to find potential partners for data exchange

As an open standard, AlpineBits is freely available and does not require a purchase. You can access the specifications and related documentation directly from the official AlpineBits website. See link
If you’re seeking software solutions that incorporate AlpineBits, several companies offer products and services compatible with the standard.
See the list of known implementations

No data is shared with AlpineBits or with the AlpineBits Alliance. Data is exclusively transmitted between partners using the AlpineBits protocol.

AlpineBits never gets your data. It is an open standard for data exchange that allows direct communication between your system (e.g., a hotel’s PMS) and the systems of your chosen partners (e.g., tourism platforms, booking engines or other service providers).

To integrate your hotel with systems that utilise the AlpineBits standard, determine if your hotel’s PMS, Channel Manager or web portal partner supports the AlpineBits standard. Many modern systems are compatible, but it’s essential to confirm this with your software provider. If your current systems do not support AlpineBits, discuss with your software provider the possibility of implementing the standard.