---
title: "OpenTravel explained: travel messaging specifications | Quantlix"
description: "OpenTravel specifications define how hotels, airlines, car rental firms and channels exchange availability, rates and bookings. Learn the 1.0 and 2.0 releases."
canonical: "https://quantlix.com/en/standards/opentravel/"
last-updated: 2026-11-16
---

Source: https://quantlix.com/en/standards/opentravel/
Language: en
Description: OpenTravel specifications define how hotels, airlines, car rental firms and channels exchange availability, rates and bookings. Learn the 1.0 and 2.0 releases.

**OpenTravel** [Product, trade and travel data](https://quantlix.com/en/standards/#exchange)

# OpenTravel: open message specifications for travel

OpenTravel is the OpenTravel Alliance message specification, used since 1999 by hotels, airlines, car rental firms and their distribution partners to exchange availability, rates, bookings and profiles in a shared format.

[Discuss your project](https://quantlix.com/en/contact/) [Read the key points](https://quantlix.com/en/standards/opentravel/#standard-overview)

## At a glance

**Full name**

OpenTravel Alliance specifications: OpenTravel 1.0 XML messages and the OpenTravel 2.0 object model (JSON and XML)

**Published by**

OpenTravel Alliance, a not-for-profit travel industry trade association founded in 1999 and run largely by volunteers

**Type**

Industry message specifications and code lists for travel distribution

**Current version**

OpenTravel 1.0 release 2024A (latest XML release offered for download); OpenTravel 2.0 release 2019A; code list maintained separately

**Applies to**

Hotels, airlines, car rental, cruise and ground transportation companies, channel managers, booking engines, GDSs and technology providers

**Last reviewed**

November 16, 2026 (2026-11-16)

## In plain terms

### Key points

- OpenTravel 1.0 defines XML request and response pairs, such as OTA\_HotelAvailRQ and OTA\_HotelAvailRS, for travel shopping and booking.
- Its shared code list gives common values for things like room amenities, so partners do not invent their own.
- OpenTravel 2.0 is an object model whose objects can be exchanged as JSON or XML, with tooling that generates API documentation.
- The specifications are free to download and implement, under license terms that require a copyright notice and acknowledgment.
- The Alliance is working with the Linux Foundation to form an open-source foundation for travel retail.

### What is OpenTravel?

OpenTravel is **a family of open message specifications for exchanging travel data between companies**. Published by the OpenTravel Alliance, a not-for-profit trade association founded in 1999, it defines how a hotel, airline, car rental company or cruise line shares availability, rates, reservations and customer profiles with the channels that sell its products.

The motivation is simple: no travel company wants to design a new format every time it connects to a partner. A specification created in an open forum and offered at no cost became a common language, and OpenTravel says hundreds of hotel, airline, cruise, car rental and ground transportation brands use its messages. Because members decide which messages are needed and build them in workgroups, the specification reflects how travel companies actually sell, rather than one vendor’s product.

### What OpenTravel covers

- **Message pairs.** OpenTravel 1.0 defines request and response messages, such as OTA\_HotelAvailRQ and OTA\_HotelAvailRS for hotel availability, plus notification messages for pushing reservations, rates and inventory.
- **Several travel sectors.** Air, hotel, car rental, cruise, ground transportation and more, sharing common building blocks for names, addresses and payments.
- **Profiles.** Customer and company profiles that travel with bookings.
- **Code list.** A shared list of coded values, such as room amenity types, maintained separately with a published change request process.
- **The 2.0 object model.** Reusable libraries of travel objects, a repository for extensions and full version management, exchanged as JSON or XML.
- **Tooling.** The open-source OTM-DEx tool turns object definitions into deployable APIs and OpenAPI documentation.

### Current status

OpenTravel is active, and **its current effort centers on the 2.0 model, tooling and open source** rather than frequent new message releases. The download page lists OpenTravel 1.0 releases up to 2024A and OpenTravel 2.0 releases up to 2019A. The Alliance describes itself as an all-volunteer non-profit and says it is working with the Linux Foundation to form an open-source foundation for travel retail, built around an offer that carries the product, price and rules together.

For integrators, that means 1.0 XML messages are still what many existing hotel and car connections use, while 2.0 and the new foundation are where future collaboration is heading.

### How it shows up in software projects

- **Partner implementation guides.** Channel managers and booking engines each document the subset and release they support, so mappings follow the partner’s guide.
- **Push and pull patterns.** Availability may be requested on demand or pushed through notification messages, and the design decides which system owns the inventory count.
- **Release differences.** Elements and attributes vary between releases such as 2015A and 2024A, so schemas are pinned per connection.
- **Code list mapping.** Internal room types, amenities and rate rules map to OpenTravel codes, with a fallback for values the partner does not support.
- **Payment and guest data.** Card details in reservations bring [PCI DSS](https://quantlix.com/en/standards/pci-dss/) scope, and profiles are personal data with access and retention rules.

### How we work with OpenTravel

We build and maintain OpenTravel integrations for booking engines, channel managers, property systems and travel platforms, including moves from older XML connections to documented JSON APIs. It underpins much of our work in [hospitality](https://quantlix.com/en/industries/hospitality/), often next to [HTNG](https://quantlix.com/en/standards/htng/) interfaces on the property side and [IATA NDC](https://quantlix.com/en/standards/iata-ndc/) for air content.

Each distribution partner decides how it tests and approves connections. We help you prepare: pinned schemas, mapped code lists, test messages and records of what each interface supports.

## Where it applies

Industries where this standard often shapes the work.

- ### [Hospitality](https://quantlix.com/en/industries/hospitality/)

  Guest experiences, booking platforms and hospitality operations

## Related standards

[All standards](https://quantlix.com/en/standards/)

- HTNG

  ### [Hotel system integration specifications](https://quantlix.com/en/standards/htng/)

  HTNG is Hospitality Technology Next Generation, the hotel technology network of the American Hotel & Lodging Association, publishing specifications that connect property management, payment, guest room and distribution systems.
- IATA NDC

  ### [Airline offer and order distribution](https://quantlix.com/en/standards/iata-ndc/)

  IATA NDC is the New Distribution Capability, an XML-based IATA standard that lets airlines send their own offers to travel sellers and manage the resulting orders, including fares, ancillaries and rich content.
- PCI DSS

  ### [Security for payment card data](https://quantlix.com/en/standards/pci-dss/)

  PCI DSS is the Payment Card Industry Data Security Standard, a set of technical and operational requirements for every organization that stores, processes or transmits payment card account data.

## Services that support this work

The services we usually bring to projects that involve this standard.

[View all services](https://quantlix.com/en/services/)

### [Enterprise applications](https://quantlix.com/en/services/enterprise-applications/)

Quantlix designs and builds enterprise applications for internal workflows, business rules and system integration, with clear access controls and maintainable architecture.

### [Web application development](https://quantlix.com/en/services/web-application-development/)

Quantlix designs and builds web applications with responsive interfaces, business logic and system integrations, balancing accessibility, performance and maintainability.

### [Legacy modernization](https://quantlix.com/en/services/legacy-modernization/)

Quantlix modernizes existing systems through targeted changes, integration and staged migration, preserving essential business behavior while addressing technical constraints.

## Questions, answered

What teams usually ask us about this standard.

**Is OpenTravel still maintained?**

Yes. In November 2026 the OpenTravel site offered OpenTravel 1.0 releases up to 2024A and OpenTravel 2.0 releases up to 2019A, along with the current code list. The Alliance describes itself as an all-volunteer non-profit and is working with the Linux Foundation to form a new open-source foundation.

**Is OpenTravel free to use?**

The OpenTravel FAQ says organizations are free to use OpenTravel messaging at no cost to download or implement. The license still applies: you must reference OpenTravel and keep its copyright notice, and you may not alter the specification itself or claim OpenTravel endorsement.

**What is the difference between OpenTravel 1.0 and 2.0?**

OpenTravel 1.0 is the long-established set of XML message schemas. OpenTravel 2.0 is an object-oriented model with reusable libraries and versioned objects that can be exchanged as JSON or XML, designed for REST APIs.

**How does OpenTravel relate to HTNG and IATA NDC?**

OpenTravel spans several travel sectors and is common in hotel and car distribution. HTNG focuses on hotel technology, especially systems on the property, while IATA NDC is the airline industry's standard for offers and orders between airlines and sellers.

**Why do OpenTravel messages start with OTA?**

The prefix comes from the Alliance's original name, the Open Travel Alliance, and stayed in the 1.0 message names, such as OTA\_HotelResNotifRQ for sending a hotel reservation.

## Official sources

Read the official text before relying on any detail. What applies to you depends on your role, your location and the version in force.

- [OpenTravel Alliance](https://opentravel.org/)
- [Download the OpenTravel specifications](https://opentravel.org/download-specs/)
- [OpenTravel 2.0 object model](https://opentravel.org/about-2-0-object-model/)
- [OpenTravel frequently asked questions](https://opentravel.org/frequently-asked-questions/)

These guides explain each standard in plain terms. They are not legal advice, and they do not state that any product or organization conforms to a standard.

## Planning software around this standard?

Tell us which systems are involved and what you need to show. We will help you build the requirements in from the start.

[Discuss your project](https://quantlix.com/en/contact/)
