Despegar · Authentication Profile

Despegar Authentication

Authentication

Despegar secures its APIs with apiKey, http, and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyConsumerTravelHotelsFlightsBookingTourismLatin AmericaB2BMCP
Methods: apiKey, http, oauth2 Schemes: 3 OAuth flows: clientCredentials API key in: header

Security Schemes

ApiKeyAuth apiKey
· in: header (x-apikey)
BearerAuth http
scheme: bearer
MCP OAuth2 oauth2

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: openapi/despegar-booking-openapi.json (+ hotels/flights/aftersales/activities/geo)
docs: https://api-docs.despegar.com/docs/security-scheme
notes: >-
  The B2B Despegar REST API is authenticated with a single API key sent in the
  x-apikey header. Keys are provisioned per client during onboarding with
  permissions tailored to the products contracted, and separate keys exist for
  the test and production environments. A JWT bearer scheme (BearerAuth) is also
  declared in the OpenAPI. The separately documented MCP B2B servers use OAuth
  2.0 client_credentials (see mcp/despegar-mcp.yml).
summary:
  types:
  - apiKey
  - http
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - clientCredentials
schemes:
- name: ApiKeyAuth
  type: apiKey
  in: header
  parameter: x-apikey
  description: Primary B2B credential; provisioned per client at onboarding, distinct test vs production keys.
  sources:
  - openapi/despegar-booking-openapi.json
  - openapi/despegar-hotels-openapi.json
  - openapi/despegar-flights-openapi.json
  - openapi/despegar-aftersales-openapi.json
  - openapi/despegar-activities-openapi.json
  - openapi/despegar-geo-openapi.json
- name: BearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  sources:
  - openapi/despegar-booking-openapi.json
  - openapi/despegar-hotels-openapi.json
  - openapi/despegar-flights-openapi.json
  - openapi/despegar-aftersales-openapi.json
  - openapi/despegar-activities-openapi.json
  - openapi/despegar-geo-openapi.json
- name: MCP OAuth2
  type: oauth2
  flow: clientCredentials
  description: OAuth 2.0 client_credentials used by the Despegar MCP B2B flights/hotels servers; credentials handled server-side.
  sources:
  - https://api-docs.despegar.com/docs/mcp-support

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact 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 security artifact 
curl "https://apis.io/api/v1/security/despegar-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

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

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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