Due · Authentication Profile

Due Authentication

Authentication

Due secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

PaymentsCross-Border PaymentsStablecoinsFintechVirtual AccountsForeign ExchangeKYCWalletsAPI
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

BearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: openapi/due-openapi-original.yml
docs: https://due.readme.io/docs/creating-customers
summary:
  types:
  - http
  http_schemes:
  - bearer
  note: >-
    Due authenticates with an API key presented as an HTTP bearer token (Authorization: Bearer <api_key>).
    Per-account operations are additionally scoped by the Due-Account-Id header. Read-only FX/market
    endpoints require no authentication. Sandbox and production use environment-specific keys/hosts.
schemes:
- name: BearerAuth
  type: http
  scheme: bearer
  description: API key presented as a bearer token.
  header: Authorization
  sources:
  - openapi/due-openapi-original.yml
account_scoping:
  header: Due-Account-Id
  note: Scopes per-account requests (see webhook fetch/retry examples).
public_endpoints:
  note: FX markets (getmarkets, getmarket, getmarkethistory) are public and require no authentication.