Introducing AlpineBits Standards
AlpineBits standards are interface specifications for the exchange of tourism data that are available for free and published under CC-BY-SA.
AlpineBits standards are built on a modular structure, providing independent features that can be used based according to your implementation needs.
The AlpineBits Alliance membership allows contribution in the defining of the AlpineBits standards.
To date, two standards have been developed by the AlpineBits Alliance:
A standard for the exchange of travel and booking information based on XML messages validated against OTA 2015A.
In the current version of the standard, the scope of AlpineBits covers the exchange of the following types of information:
- reservation inquiries (GuestRequests)
- room category information (Inventory)
- room availability (FreeRooms)
- prices (RatePlans)
- hotel internal activities (ActivityData)
AlpineBits DestinationData Standard
A standard to enable the exchange of events and mountain resort related information, an OntoUML ontology has been built to describe the conceptualisation and scope of the standard.
In the current version of the standard, the scope of AlpineBits covers the exchange of the following types of information:
- events, events series and venues
- mountain areas
- trails and lifts
- snow measurements
AlpineBits FAQs
AlpineBits HotelData Technical Questions
How do I install AlpineBits?
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 known implementations
How do I upload/download data to/from AlpineBits?
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 implementations
Where can I find the AlpineBits documentation?
Should I implement my API as a “server” or as a “client”?
In AlpineBits terminology, the “client” always initiates communication. In general, PMSs are clients, while web portals or channel managers are servers.
What is the purpose of AlpineBits “Handshaking”?
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.
How does AlpineBits “Handshaking” work?
During Handshaking, partners exchange a message where they declare the protocol versions and functionalities they support.
Can I send data to a server/client using a different AlpineBits version than my client/server?
No, mixing AlpineBits HotelData version is not allowed.
How do I send/receive requests or bookings?
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.
How do I test my API implementation?
You can use the AlpineBits testing tool available at the following link: Link to testing tool
What are the specific steps required to implement a certified interface according to the AlpineBits standard?
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
What technical prerequisites and specifications need to be met?
The requirements depend on the specific implementation. However, a stable and reliable connection is essential, particularly for servers waiting to handle client requests.
What kind of documentation is required or provided to support the implementation?
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
Do I have to implement all the actions mentioned in the documentation?
No. The protocol is modular, so you only need to implement the messages relevant to your use case. However, Handshaking is mandatory.
Can I also exchange information about events?
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.
For HotelData, only activities directly related to the accommodation facility are managed.
Which version of AlpineBits is best to implement?
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.
Certification Questions
What are the specific steps required to certify the interface according to the AlpineBits standard?
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
What does the testing process for certification involve?
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.
What is the purpose of certification?
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.
How does the certification process work?
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:
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.
How long does the whole certification process typically take?
Approx, 4-6 weeks however it depends on the correctness of your implementation.
What are the overall costs associated with the certification?
General Questions
Is it possible to get a list of portals that support your protocol?
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
Where can I buy AlpineBits and how much does it cost?
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
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
Who owns my data and under what licence after I have sent it to AlpineBits?
No data is shared with AlpineBits or with the AlpineBits Alliance. Data is exclusively transmitted between partners using the AlpineBits protocol.
To whom does AlpineBits send my data?
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).
How do I register my hotel on AlpineBits?
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.
Membership Questions
How do I become a Member?
Fill in the form and apply for membership. Go to the membership form
How can I contribute to the development of AlpineBits?
Participating in the development of AlpineBits allows you to contribute to the evolution of open standards in tourism data exchange. Here’s how you can get involved:
- Join the AlpineBits Alliance: Becoming a member provides access to task forces, technical discussions, and the opportunity to influence the future of AlpineBits standards. More info
- Contribute to the Git Repositories: The AlpineBits specifications and tools are maintained in public Git repositories. You can contribute by submitting suggestions, reporting issues, or providing code improvements. Visit our public repositories
Do I need to become a member to implement AlpineBits?
No, you do not need to become a member to implement AlpineBits. The protocol is openly available and you can freely use its specifications to develop your implementation. However, while membership is not required, joining the AlpineBits Alliance offers certain benefits. Membership is necessary if you wish to actively participate in the Alliance’s decision-making and development processes.
AlpineBits Alliance
c/o NOI Techpark – Building D3
via Gianni Brida 4 | Gianni-Brida-Straße 4
I-39100 Bolzano | Bozen
c/o NOI Techpark – Building D3
via Gianni Brida 4 | Gianni-Brida-Straße 4
I-39100 Bolzano | Bozen
VAT ID: IT02797280217 E-Mail: info@alpinebits.org
