This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
Not from the company, and here with a question? You are welcome here — we would rather be the front line and point you the right way than have a good report go nowhere. What this repository can answer is narrow, though, so it is worth knowing who you are actually looking for:
- A question about how the API works, an account, billing, or a bug in the service — that is the company's own support, not us. We profile this API; we do not operate it and cannot see your account.
- A bug in an open-source project we only catalog — file it on that project's own repository. This has happened with a real and correct bug report that reached us instead of the people who could fix it, which helped nobody.
- Anything about this listing itself — the description, the tags, the rating, a missing or wrong artifact — is ours. Open an issue here.
- Not sure, or something general about API Evangelist or APIs.io — open an issue on the APIs.io Inbox and we will route it.
This repository contains no software, and we will never ask you to download anything. There is no build, release, installer, or binary here — only text and machine-readable API descriptions, so there is nothing here that can be "corrupt" or need "repairing". Any issue, comment, or email claiming otherwise and offering a download link is not from us and is hostile. Do not follow the link; it is a lure. Report it to GitHub and, if you like, tell us at info@apievangelist.com so we can take it down.
On a security or compliance team? Email info@apievangelist.com with 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 so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
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 self-serve developer portal, no OpenTravel-operated runtime API and no public certification registry. 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.
APIs.json: https://raw.githubusercontent.com/api-evangelist/opentravel-alliance/refs/heads/main/apis.yml
- Travel
- United States
- Standards
- Aviation
- Hospitality
- Hotels
- Car Rental
- Rail
- Cruise
- Distribution
- GDS
- Booking
- Channel
- XML
- JSON Schema
- Created: 2026-07-28
- Modified: 2026-07-28
Swagger 2.0 resource contract generated from the OpenTravel 2.0 Object Model, 2020A Object Suite. Defines three operations for hotel descriptive content — GET /HotelDescriptiveContents, POST /HotelDescriptiveContents/Query and POST /HotelDescriptiveContents/Notifications — with 337 model definitions. This is a specification artifact published by the standards body for implementers to host themselves; the document declares host 127.0.0.1 and basePath /v1_0 and OpenTravel operates no runtime endpoint for it.
- Human URL: https://github.com/OpenTravel/OpenTravel-Specifications/tree/master/OTA2.0/OTA2.0_2020A_ObjectSuite
- Hospitality
- Hotels
- Content
- OpenTravel 2.0
Swagger 2.0 resource contract generated from the OpenTravel 2.0 Object Model, 2020A Object Suite. Defines POST /Facilities and GET /Facilities/{Identifier} with 232 model definitions covering hospitality and golf facility description. Published as a specification artifact with host example.com and basePath /resource/v1_0; OpenTravel operates no runtime endpoint for it.
- Human URL: https://github.com/OpenTravel/OpenTravel-Specifications/tree/master/OTA2.0/OTA2.0_2020A_ObjectSuite
- Hospitality
- Facilities
- OpenTravel 2.0
Swagger 2.0 resource contract generated from the OpenTravel 2.0 Object Model, 2018A Object Suite. Defines POST /HospitalityOffers and POST /HospitalityPropertyOffers with 372 model definitions covering hotel offer search and property-level offers. Specification artifact only — host 127.0.0.1, basePath /; the definitions variant of this file is Latin-1 encoded rather than UTF-8 as published upstream.
- Human URL: https://github.com/OpenTravel/OpenTravel-Specifications/tree/master/OTA2.0/OTA2.0_2018A_ObjectSuite
- Hospitality
- Hotels
- Offers
- OpenTravel 2.0
Swagger 2.0 resource contract generated from the OpenTravel 2.0 Object Model, 2018A Object Suite. Defines POST /Facilities, POST /HospitalityFindHospitalityAvailability and POST /HospitalityRetrieveFacilityAvailability with 187 model definitions. Specification artifact only — host 127.0.0.1, basePath /; the definitions variant of this file is Latin-1 encoded rather than UTF-8 as published upstream.
- Human URL: https://github.com/OpenTravel/OpenTravel-Specifications/tree/master/OTA2.0/OTA2.0_2018A_ObjectSuite
- Hospitality
- Facilities
- Availability
- OpenTravel 2.0
- Website
- About
- Specifications
- Documentation — About the OpenTravel 2.0 Object Model
- Download — the OpenTravel Specification (lead-capture form)
- Download — the OpenTravel Code List
- Download — the OTM Development Environment (DEx)
- Repository — OpenTravel-Specifications public GitHub mirror
- GitHub Organization
- Registry — OTM Library Repository console (login required)
- Directory — OpenTravel Message Adopters and Integrators
- Pricing — membership dues by revenue band
- Sign Up
- Terms of Service
- Privacy Policy
- License — OpenTravel Intellectual Property Policy
- Governance
- Partners
- Blog
- Contact
- FAQ
Recorded in full in review.yml.
- Interface shape:
open-standard— the OpenTravel Specification (OTA 1.0 XML message suite, OpenTravel 2.0 Object Model). The interface is the product, and it is royalty-free and multi-implementer. - Second source:
alternatives-with-migration— IATA NDC, IATA ONE Order, HTNG, GDS-proprietary formats and direct supplier REST APIs all address overlapping ground. Swapping OpenTravel for HTNG is a schema-mapping project; swapping air messaging for NDC is a rebuild. - Exit path:
not-applicable— OpenTravel holds no customer data and operates no runtime. A copy of a member's OTM repository can be requested for use with GitHub. - Identifier portability: IATA airline and airport codes, hotel chain and brand codes, ISO country and currency codes carried in the OpenTravel Code Lists and OTM CodeList schema modules. No PNR locators, no GDS record IDs, no OpenTravel-owned opaque identifiers.
- Contractual lock-in: none published beyond a terminable, attribution-bearing specification licence. Immediate termination on breach requires ceasing all use and distribution. The membership agreement — the one document that would settle the member-side commitment — is not published.
- Access gate:
application-approval— a name/company/email form plus terms acceptance for the specification; a justified request form for the OTM repository and the LinksRez portal; $950–$11,250/yr membership to extend the model or influence priorities. The public GitHub mirror is the one ungated route, and it carries no LICENSE file. - Distribution model:
not-applicable— OpenTravel is the vocabulary that GDS-intermediated, channel-manager and direct-connect distribution all speak, not a distributor. - NDC posture: not applicable — OpenTravel is a peer of IATA, runs its own Offer/Order workgroup, claims no NDC certification level and publishes no NDC endpoint.
Eight Swagger 2.0 documents, fetched verbatim on 2026-07-28 from raw.githubusercontent.com (HTTP 200 on each), all from the public OpenTravel/OpenTravel-Specifications mirror at commit "Initial commit" (2024-11-26). Full provenance in review.yml.
The mirror carries 19,066 files in total: 10,848 XSD, 5,823 XML, 1,255 HTML, 543 JSON Schema, 181 PDF, 39 ZIP, 22 WSDL and 8 Swagger. Its OTA 1.0 tree stops at release 2017B while the website download form offers releases through 2024A — the public mirror is seven years behind the gated one.