Airwallex · Authentication Profile

Airwallex Authentication

Authentication

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

Cross-Border PaymentsFintechForeign ExchangePaymentsGlobalEmbedded FinanceMulti-Currency
Methods: apiKey, http, oauth2 Schemes: 4 OAuth flows: authorizationCode API key in: header

Security Schemes

BearerAuth http
scheme: bearer
ClientIdHeader apiKey
· in: header (x-client-id)
ApiKeyHeader apiKey
· in: header (x-api-key)
AirwallexOAuth oauth2
· flows: authorizationCode

Source

Authentication Profile

Raw ↑ 
generated: '2026-08-30'
method: searched
source: https://www.airwallex.com/docs/api/getting_started
summary:
  types:
  - apiKey
  - http
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - authorizationCode
  token_lifetime: 30 minutes
  token_endpoint: POST /api/v1/authentication/login
schemes:
- name: BearerAuth
  type: http
  scheme: bearer
  description: 'Bearer access token obtained via POST /api/v1/authentication/login using

    `x-client-id` and `x-api-key` request headers.'
  sources:
  - openapi/airwallex-authentication-api-openapi.yml
  - openapi/airwallex-balances-api-openapi.yml
  - openapi/airwallex-beneficiaries-api-openapi.yml
  - openapi/airwallex-customers-api-openapi.yml
  - openapi/airwallex-payment-intents-api-openapi.yml
  - openapi/airwallex-payouts-api-openapi.yml
  - openapi/airwallex-refunds-api-openapi.yml
  - openapi/airwallex-transfers-api-openapi.yml
- name: ClientIdHeader
  type: apiKey
  in: header
  parameter: x-client-id
  sources:
  - openapi/airwallex-authentication-api-openapi.yml
  - openapi/airwallex-balances-api-openapi.yml
  - openapi/airwallex-beneficiaries-api-openapi.yml
  - openapi/airwallex-customers-api-openapi.yml
  - openapi/airwallex-payment-intents-api-openapi.yml
  - openapi/airwallex-payouts-api-openapi.yml
  - openapi/airwallex-refunds-api-openapi.yml
  - openapi/airwallex-transfers-api-openapi.yml
- name: ApiKeyHeader
  type: apiKey
  in: header
  parameter: x-api-key
  sources:
  - openapi/airwallex-authentication-api-openapi.yml
  - openapi/airwallex-balances-api-openapi.yml
  - openapi/airwallex-beneficiaries-api-openapi.yml
  - openapi/airwallex-customers-api-openapi.yml
  - openapi/airwallex-payment-intents-api-openapi.yml
  - openapi/airwallex-payouts-api-openapi.yml
  - openapi/airwallex-refunds-api-openapi.yml
  - openapi/airwallex-transfers-api-openapi.yml
- name: AirwallexOAuth
  type: oauth2
  flows:
  - flow: authorizationCode
    scopes: 98
    consent_roles:
    - Owner
    - Admin
    - Finance Admin
  audience: third-party partner applications, the Airwallex CLI, and the hosted MCP servers
  sources:
  - https://www.airwallex.com/docs/developer-tools/partner-connections/oauth-scopes
  - https://mcp.airwallex.com/.well-known/oauth-protected-resource/mcp/
  scopes_artifact: scopes/airwallex-scopes.yml
  revocation: https://www.airwallex.com/app/integrations/home
docs:
  getting_started: https://www.airwallex.com/docs/api/getting_started
  manage_api_keys: https://www.airwallex.com/docs/developer-tools/api/manage-api-keys
  api_key_best_practices: https://www.airwallex.com/docs/developer-tools/api/api-key-best-practices
  oauth_scopes: https://www.airwallex.com/docs/developer-tools/partner-connections/oauth-scopes
note: Upgraded from derived to searched. The three schemes below were confirmed against the provider's own Get started
  page, and the OAuth model - which the OpenAPI in this repo does not carry at all - was added from the partner-connections
  scope reference and the live RFC 9728 metadata on the hosted MCP servers.
token:
  endpoint: POST https://api.airwallex.com/api/v1/authentication/login
  sandbox_endpoint: POST https://api.sandbox.airwallex.com/api/v1/authentication/login
  request_headers:
  - x-client-id
  - x-api-key
  - 'Content-Type: application/json'
  response_fields:
  - token
  - expires_at
  lifetime: 30 minutes
  call_header: 'Authorization: Bearer <token>'
  rate_limit: 100 requests per minute per API key (fixed, environment-independent)
  reuse_required: true
delegation:
  header: x-on-behalf-of
  value: connected account id
  note: platform credentials plus this header call any endpoint for a connected account; no per-account credentials
    are issued
key_management:
  location: Account > Developer > API keys in the Airwallex web app
  environment_separation: separate keys per environment; NO test/live key prefix
  best_practices: https://www.airwallex.com/docs/developer-tools/api/api-key-best-practices
environments:
- name: production
  base: https://api.airwallex.com/api/v1
- name: sandbox
  base: https://api.sandbox.airwallex.com/api/v1
sources:
- https://www.airwallex.com/docs/api/getting_started

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/airwallex-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.