Breeze · Authentication Profile

Breeze Authentication

Authentication

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

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

Security Schemes

api_key apiKey
· in: header (x-api-key)
bearer_auth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: openapi/breeze-openapi-original.json
docs: https://docs.breeze.baby/get-your-api-key/instruction
notes: >-
  Integration endpoints authenticate with an API key in the x-api-key header
  (generated in the Breeze Customer Portal, portal.breeze.baby). Organization and
  admin endpoints use a JWT bearer token. The x402 Agent Kit path is keyless,
  gated by USDC micropayments instead.
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: api_key
  type: apiKey
  in: header
  parameter: x-api-key
  sources:
  - openapi/breeze-openapi-original.json
- name: bearer_auth
  type: http
  scheme: bearer
  bearerFormat: JWT
  sources:
  - openapi/breeze-openapi-original.json