TUI Group · OAuth Scopes

TUI Group OAuth Scopes

OAuth 2.0 derived

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

Tokens are issued from https://prod.api.tui/oauth2/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 KingdomAviationAirlineTour OperatorDistributionNDCHospitalityHotelsCruiseBookingPackagesMetasearch

Scopes: 1 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://prod.api.tui/oauth2/token https://pre-prod.api.tui/oauth2/token

Flows
clientCredentials

Scopes (1)

Scope	Description	Flows
read:sales-meta-package	Read access	clientCredentials

📄 Provider scope reference: https://developer.tui/docs/general/oauth2

Source

OAuth Scopes

generated: '2026-07-28'
method: derived
source: openapi/tui-group-tui-b2bota-g7-travelmessage-openapi.yml, openapi/tui-group-tui-flight-ota-api-openapi.yml,
  openapi/tui-group-tui-meta-partner-package-live-search-openapi.yml, openapi/tui-group-tui-meta-partner-packages-flights-openapi.yml,
  openapi/tui-group-tui-meta-search-generic-api-openapi.yml
docs: https://developer.tui/docs/general/oauth2
search:
  performed: '2026-07-28'
  probes:
  - {url: 'https://developer.tui/docs/general/scopes', status: 404}
  - {url: 'https://developer.tui/docs/general/permissions', status: 404}
  - {url: 'https://developer.tui/docs/scopes', status: 404}
  - {url: 'https://developer.tui/docs/general/oauth2', status: 200}
  - {url: 'https://developer.tui/docs/general/authentication', status: 200}
  conclusion: >-
    TUI publishes no scopes or permissions reference page. The OAuth 2.0 page documents the
    client-credentials grant against https://{env}.api.tui/oauth2/token and shows a token response
    carrying a scope field, but the sample value is the literal placeholder "scope1 scope2" and no
    scope name, meaning or requirement is documented anywhere on the portal. Authorisation at TUI is
    not scope-driven: what a token can reach is decided by which API products a partner manager
    approved for the app, plus the Navitaire New Skies agent role behind the flight products. The
    single real scope below is the only one declared in any of the 21 published specs. Recorded as
    derived because the docs search added nothing the specs did not already carry.
schemes:
- name: oAuth2ClientCredentials
  source: openapi/tui-group-tui-b2bota-g7-travelmessage-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://prod.api.tui/oauth2/token
  description: This API uses OAuth 2 with the implicit grant flow.
- name: oAuth2ClientCredentials
  source: openapi/tui-group-tui-flight-ota-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://prod.api.tui/oauth2/token
- name: tsoa_auth_prod
  source: openapi/tui-group-tui-meta-partner-package-live-search-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://prod.api.tui/oauth2/token
  description: Production OAuth2
- name: tsoa_auth_preprod
  source: openapi/tui-group-tui-meta-partner-package-live-search-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://pre-prod.api.tui/oauth2/token
  description: Pre-production OAuth2
- name: tsoa_auth_prod
  source: openapi/tui-group-tui-meta-partner-packages-flights-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://prod.api.tui/oauth2/token
  description: Production OAuth2
- name: tsoa_auth_preprod
  source: openapi/tui-group-tui-meta-partner-packages-flights-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://pre-prod.api.tui/oauth2/token
  description: Pre-production OAuth2
- name: OAuth2PreProdPublic
  source: openapi/tui-group-tui-meta-search-generic-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://pre-prod.api.tui/oauth2/token
- name: OAuth2ProdPublic
  source: openapi/tui-group-tui-meta-search-generic-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://prod.api.tui/oauth2/token
scopes:
- scope: read:sales-meta-package
  description: Read access
  flows:
  - clientCredentials
  sources:
  - openapi/tui-group-tui-meta-partner-package-live-search-openapi.yml
  - openapi/tui-group-tui-meta-partner-packages-flights-openapi.yml

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/tui-group-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.