Bridge · Authentication Profile

Bridge Authentication

Authentication

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

CompanyCryptoStablecoinsPaymentsMoney MovementCross-Border PaymentsVirtual AccountsWalletsCardsFintech
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

ApiKey apiKey
· in: header (Api-Key)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: openapi/bridge-openapi-original.json
docs: https://apidocs.bridge.xyz/api-reference/api-keys/create-a-scoped-api-key
summary:
  types:
  - apiKey
  api_key_in:
  - header
schemes:
- name: ApiKey
  type: apiKey
  in: header
  parameter: Api-Key
  sources:
  - openapi/bridge-openapi-original.json
scoped_keys:
  supported: true
  scopes_artifact: scopes/bridge-scopes.yml
  scope_count: 68
  max_scoped_keys_per_developer: 500
  subsetting: Callers may only grant scopes they themselves hold; scoped keys need the api_key:create scope to mint further keys.
environments:
- name: production
  base_url: https://api.bridge.xyz/v0
  key_prefix: null
- name: sandbox
  base_url: https://api.sandbox.bridge.xyz/v0
  key_prefix: sk-test
notes: >
  Every request authenticates with a static API key passed in the Api-Key header.
  Keys are generated in the Bridge dashboard and may be unrestricted or scoped to a
  subset of the 68 available scopes. Sandbox keys are prefixed sk-test and target
  the sandbox base URL. There is no OAuth2 / OpenID Connect flow.