OpenTravel Alliance OAuth Scopes

OAuth 2.0 searched

OpenTravel Alliance publishes 1 OAuth 2.0 scope via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the OpenTravel Alliance API on a user’s behalf.

Tokens are issued from https://opentravel.org/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

TravelUnited StatesStandardsAviationHospitalityHotelsCar RentalRailCruiseDistributionGDSBookingChannelXMLJSON-Schema

Scopes: 1 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://opentravel.org/oauth/authorize

Token URL
https://opentravel.org/oauth/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
mcp	Access the OpenTravel Model Context Protocol server at https://opentravel.org/wp-json/mcp/mcp-oauth-server. Advertised as scopes_supported by both the RFC 8414 authorization-server metadata and the RFC 9728 protected-resource metadata.	authorizationCode

📄 Provider scope reference: https://opentravel.org/.well-known/oauth-protected-resource

Source

OAuth Scopes

generated: '2026-07-28'
method: searched
source: https://opentravel.org/.well-known/oauth-authorization-server
docs: https://opentravel.org/.well-known/oauth-protected-resource
note: >-
  The published OpenTravel Swagger 2.0 contracts declare no oauth2 security schemes, so
  derive-oauth-scopes.py returned nothing for this provider. The scope surface below is the
  real one advertised by the OAuth 2.1 authorization server that opentravel.org runs in front
  of its Model Context Protocol endpoints. It is a single coarse scope; there is no per-tool
  or per-resource scope decomposition published, and none is invented here.
schemes:
- name: opentravel-mcp-oauth
  source: well-known/opentravel-alliance-oauth-authorization-server.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://opentravel.org/oauth/authorize
    tokenUrl: https://opentravel.org/oauth/token
scopes:
- scope: mcp
  description: >-
    Access the OpenTravel Model Context Protocol server at
    https://opentravel.org/wp-json/mcp/mcp-oauth-server. Advertised as scopes_supported by
    both the RFC 8414 authorization-server metadata and the RFC 9728 protected-resource
    metadata.
  flows: [authorizationCode]
  sources:
  - well-known/opentravel-alliance-oauth-authorization-server.json
  - well-known/opentravel-alliance-oauth-protected-resource.json

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/opentravel-alliance-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.