OpenTravel Alliance
The OpenTravel Alliance is a volunteer, non-profit travel technology standards body headquartered in Melbourne, Florida, United States. Since 1999 it has published the OpenTravel Specification — the OTA 1.0 XML message suite (releases 2001A through 2024A) and the model-driven OpenTravel 2.0 Object Model (OTM), which generates XML Schema, JSON Schema and Swagger 2.0 resource contracts — plus the OpenTravel Code Lists used across air, hospitality, car rental, cruise, rail, GDS, channel and technology-provider systems. OpenTravel does not operate a booking service or sit in the distribution chain itself; it supplies the message vocabulary that suppliers, GDSs, channel managers and OTAs implement between each other, which makes it a switching-cost reducer rather than a switching-cost holder. Its API posture is honest but thin: there is no OpenTravel-operated runtime API and no public certification registry, though it does run a free self-serve developer portal — the OpenTravel Developers Network at opentraveldevelopersnetwork.com — and, as of 2026, an OAuth 2.1 protected Model Context Protocol server on opentravel.org. Specifications are royalty-free and free of charge, but the canonical download is behind a name/company/email lead-capture form with terms acceptance, and the OTM repository and member review periods are membership-gated ($950–$11,250/yr by revenue band). A public, unlicensed GitHub mirror at github.com/OpenTravel/OpenTravel-Specifications carries the bulk of the corpus — including eight Swagger 2.0 resource contracts — and is the only ungated route to machine-readable artifacts. The organization has announced work with the Linux Foundation to form an Open Travel Foundation.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles OpenTravel Alliance the way a machine reads it — 37 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — OpenTravel Alliance scores 44.3/100 (developing), with a separate agent-readiness read of 47/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from OpenTravel Alliance's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/opentravel-alliance/"
title="OpenTravel Alliance on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/opentravel-alliance.svg"
alt="OpenTravel Alliance Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/opentravel-alliance/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/opentravel-alliance/"
title="OpenTravel Alliance on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/opentravel-alliance/card.svg"
alt="OpenTravel Alliance Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile OpenTravel Alliance
Each block below is one kind of artifact we hold for OpenTravel Alliance. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
OpenTravel Alliance Facilities API
The Facilities API from OpenTravel Alliance — 2 operation(s) for facilities.
OpenTravel Alliance Hospitality Find Hospitality Availability API
The HospitalityFindHospitalityAvailability API from OpenTravel Alliance — 1 operation(s) for hospitalityfindhospitalityavailability.
OpenTravel Alliance Hospitality Offers API
The HospitalityOffers API from OpenTravel Alliance — 1 operation(s) for hospitalityoffers.
OpenTravel Alliance Hospitality Property Offers API
The HospitalityPropertyOffers API from OpenTravel Alliance — 1 operation(s) for hospitalitypropertyoffers.
OpenTravel Alliance Hospitality Retrieve Facility Availability API
The HospitalityRetrieveFacilityAvailability API from OpenTravel Alliance — 1 operation(s) for hospitalityretrievefacilityavailability.
OpenTravel Alliance Hotel Descriptive Contents API
The HotelDescriptiveContents API from OpenTravel Alliance — 3 operation(s) for hoteldescriptivecontents.
Open Collections 8
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
FacilityResource
OPEN COLLECTIONFacilityResource
OPEN COLLECTIONHospitalityOffersResource
OPEN COLLECTIONHospitalityOffersResource
OPEN COLLECTIONFacilityResource
OPEN COLLECTIONFacilityResource
OPEN COLLECTIONHotelDescriptiveContentResource
OPEN COLLECTIONHotelDescriptiveContentResource
OPEN COLLECTIONScroll within the panel for all 8 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
JSON Schema 10
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CodeList
JSON SCHEMAHospitalityFacility
JSON SCHEMAHospitalityOffers
JSON SCHEMACodeList
JSON SCHEMACodeList
JSON SCHEMACommon
JSON SCHEMAFacilityResource
JSON SCHEMAHospitalityContent
JSON SCHEMAOrganization
JSON SCHEMAOrganizationHospitality
JSON SCHEMAScroll within the panel for all 10 ·
Examples 7
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 7 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for OpenTravel Alliance — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 6
Reference material describing how the API behaves
Agent Surfaces 9
MCP servers, agent skills, and machine-readable catalogs
Scroll within the panel for all 9 ·
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 7
Status, limits, changes, and where to get help
Scroll within the panel for all 7 ·
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 12
Properties that don't map to a standard resource type
Scroll within the panel for all 12 ·
← All providers · Data indexed from github.com/api-evangelist/opentravel-alliance · machine-readable index on apis.io
This is an independent, third-party profile of OpenTravel Alliance, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.