Consola Finance · Authentication Profile

Consola Finance Authentication

Authentication

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

CompanyCrypto AccountingDigital AssetsWeb3 FinanceAccounts PayableAccounts ReceivableInvoicingPayrollBookkeepingBlockchain
Methods: apiKey, oauth2 Schemes: 2 OAuth flows: authorizationCode, clientCredentials API key in: header

Security Schemes

ApiKey apiKey
· in: header (Authorization)
OAuth2 oauth2
· flows: authorizationCode, clientCredentials

Source

Authentication Profile

consola-finance-authentication.yml Raw ↑ 
generated: '2026-07-18'
method: searched
source: https://docs.request.finance/getting-started
docs: https://docs.request.finance/going-live
notes: >-
  Request Finance API auth, captured from the docs (no OpenAPI is published).
  Two modes: API key (Bearer-style Authorization header) for quick start, and
  OAuth 2.0 (Auth0-backed at auth.request.finance) for production. Endpoints and
  scopes cross-checked against the live OIDC discovery document saved under
  well-known/.
summary:
  types: [apiKey, oauth2]
  api_key_in: [header]
  api_key_header: Authorization
  oauth2_flows: [authorizationCode, clientCredentials]
  extra_headers:
  - name: X-Network
    values: [test, live]
    required: true
    description: Selects the test (Sepolia testnet) or live environment.
schemes:
- name: ApiKey
  type: apiKey
  in: header
  parameter: Authorization
  description: >-
    Bearer API key from the Developer tab in Settings
    (https://app.request.finance/account/api-keys). Separate Test and Live keys.
    Docs note API keys are being deprecated in favor of OAuth for live apps.
- name: OAuth2
  type: oauth2
  issuer: https://auth.request.finance/
  audience: accounts
  authorizationUrl: https://auth.request.finance/authorize
  tokenUrl: https://auth.request.finance/oauth/token
  flows:
  - flow: authorizationCode
    use: act on a user's behalf (read their invoices); returns access + refresh tokens
  - flow: clientCredentials
    use: act on your own account (send invoices); access token only, activation required
  access_token_ttl: 24h
  default_scopes: [openid, profile, email, offline_access]