WeTravel · Authentication Profile

Wetravel Authentication

Authentication

WeTravel secures its APIs with apiKey and http across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyBusiness ApplicationsTravelBookingPaymentsTrip ManagementTour OperatorsTravel Technology
Methods: apiKey, http Schemes: 2 OAuth flows: API key in: header

Security Schemes

bearerAuth http
scheme: bearer
tokenAuth apiKey
· in: header (X-Api-Key)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: derived
source: openapi/wetravel-partner-openapi.json
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  sources:
  - openapi/wetravel-partner-openapi.json
- name: tokenAuth
  type: apiKey
  in: header
  parameter: X-Api-Key
  sources:
  - openapi/wetravel-partner-openapi.json

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/wetravel-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 email required.

GitHub Google LinkedIn

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