Wallex · Authentication Profile

Wallex Authentication

Authentication

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

CompanyPaymentsCross-Border PaymentsForeign ExchangeFintechCollectionB2B PaymentsEmbedded FinanceSoutheast Asia

Methods: apiKey, http Schemes: 2 OAuth flows: API key in: header

Security Schemes

ApiKeyAuth apiKey

· in: header ()

BearerAuth http

scheme: bearer

Source

Authentication Profile

generated: '2026-07-21'
method: searched
source: https://docs.wallex.asia/docs/intro
docs:
- https://docs.wallex.asia/docs/intro
- https://docs.wallex.asia/docs/api/authentication/authenticate
- https://docs.wallex.asia/docs/api/authentication/authenticate-yaml
summary:
  types: [apiKey, http]
  api_key_in: [header]
  model: >-
    Two-layer auth. Every request carries a static X-Api-Key header for
    identification. Restricted resources additionally require a short-lived
    Bearer token (Authorization header) obtained by exchanging accessKeyId +
    secretAccessKey at POST /v2/authenticate. Tokens are valid for 8 hours and
    can be refreshed at any time; Log Out invalidates a token before expiry.
credentials:
  provisioning: Credentials are issued by Wallex on request (contact@wallextech.com); there is no self-serve key page for the Partner API.
  items:
  - name: X-Api-Key
    description: Static key that identifies the partner on every request. Missing/invalid returns 403 Forbidden.
  - name: accessKeyId
    description: Used with secretAccessKey to obtain the authorization token.
  - name: secretAccessKey
    description: Used with accessKeyId to obtain the authorization token.
schemes:
  - name: ApiKeyAuth
    type: apiKey
    in: header
    parameter_name: X-Api-Key
    required: always
    source: docs
  - name: BearerAuth
    type: http
    scheme: bearer
    bearer_format: opaque-token
    token_endpoint: POST /v2/authenticate
    token_ttl_seconds: 28800
    required: restricted-resources
    revocation: POST /v2/logout
    source: docs
missing_header_behavior:
  no_api_key: 403 Forbidden
  no_authorization: 401 Unauthorized

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