HTNG is the hospitality industry’s interface standards programme — the specifications that let a property management system, a channel manager, a revenue management system, a point of sale and a door lock exchange data without a bespoke integration for each pair. Founded in 2002 and now part of the American Hotel & Lodging Association, it publishes workgroup-authored interface specifications rather than a single monolithic standard.
HTNG
HTNG exists because a hotel runs on a dozen systems that must talk to each other — property management, channel management, revenue management, point of sale, guest room technology, door locks, energy — and the alternative to a standard is an integration per pair per vendor. Founded in 2002 and now operating under the American Hotel & Lodging Association, HTNG produces workgroup-authored interface specifications rather than one unified spec, which is both its strength and its ceiling.
- Interface-scoped, not domain-scoped - specifications cover a named integration point between two system classes, produced by a workgroup of the vendors who implement it.
- Vendor-driven - the workgroups are staffed by the technology providers, which makes the output practical and makes coverage uneven.
- Complementary to OpenTravel - HTNG interfaces frequently carry OpenTravel message payloads rather than defining a competing vocabulary.
What the evidence shows
Across the travel quartet, HTNG is the least visible of the three standards programmes in the sector — behind NDC in air and OpenTravel in messaging — and its absence from published evidence is the finding.
The State of US Travel APIs scored the hospitality technology tier at 49.0, the third-strongest tier in the market, on the strength of two vendors: Oracle Hospitality’s 59 specifications — the deepest published surface in US travel, the OPERA property-management surface most large hotels run on, and the top-scoring organization in the market at 55.9 — and Cloudbeds’ 29 for independent properties. Neither publishes against a named HTNG interface specification in its public contract. Meanwhile the hotel groups those systems serve average 22.3, and HEDNA, the hospitality distribution trade body, scores 14.1 — below most of its own members.
The State of Australian Travel APIs is blunter: not one organization in that market publishes an interface conforming to HTNG, OpenTravel or an NDC schema version. SiteMinder — a global channel manager connecting more than 53,000 properties to over 450 distribution channels, occupying exactly the position HTNG interfaces were written for — publishes a developer portal documenting five integration APIs, scores 18.7, and registers no machine-readable contract and zero on every agent-readiness dimension.
The transferable reading is the one the whole travel quartet supports: in hospitality, the integration layer is a commercial asset, and a standard that makes it substitutable is adopted internally and published rarely.
Referenced in API Evangelist papers
This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.
The State of US Travel APIs
One of three standards programmes in a sector whose published corpus still cannot agree whether the resource is `booking` or `bookings`.
The State of Australian Travel APIs
Not one Australian travel organization publishes an interface conforming to HTNG, OpenTravel or an NDC schema version.
