Chariot · Authentication Profile

Chariot Authentication

Authentication

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

PaymentsDonor Advised FundsCharitable GivingNonprofitFintechDAFpayGrantsDisbursementsOpen BankingFDXWebhooksCompany
Methods: http, oauth2 Schemes: 2 OAuth flows: authorizationCode API key in:

Security Schemes

oauth2 oauth2
· flows: authorizationCode
bearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: openapi/chariot-fdx-openapi-original.yml, openapi/chariot-openapi-original.yml, well-known/chariot-openid-configuration.json
docs: https://docs.givechariot.com/api/authentication
notes: >-
  Two auth models. The core REST API uses HTTP bearer with secret keys (test prefix sk_test_) over
  TLS 1.2+ in the Authorization header. The FDX (open-banking) API uses OAuth 2.0 authorization_code.
  OIDC discovery at /.well-known/openid-configuration advertises grant types authorization_code,
  refresh_token, client_credentials, and token-exchange; PKCE S256; and private_key_jwt client auth.
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - authorizationCode
schemes:
- name: oauth2
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://dashboard.givechariot.com/oauth/authorize
    tokenUrl: https://api.givechariot.com/auth/oauth/token
    scopes: 2
  description: OAuth 2.0 Bearer token. A client may hold both scopes, but each FDX authorization
    must contain exactly one — they are mutually exclusive per authorization. An authorization
    containing both will be rejected. See the Authentication page for token exchange details.
  sources:
  - openapi/chariot-fdx-openapi-original.yml
- name: bearerAuth
  type: http
  scheme: bearer
  sources:
  - openapi/chariot-openapi-original.yml