Upward Financial · Authentication Profile

Upward Financial Authentication

Authentication

The Upward (Upwardli) Credit Suite API uses OAuth 2.0 for machine-to-machine authentication. Partners obtain a Bearer access token from the dedicated Authorization service (client_credentials grant with client_id + client_secret and requested scopes), then pass it in the Authorization header of every API request. A second endpoint implements RFC 8693 OAuth token exchange to down-scope a partner token to a single consumer (consumer:), producing a limited token that is safe to ship to a client application or browser. The OpenAPI declares the resulting Bearer scheme (http bearer).

Upward Financial secures its APIs with http and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials and token-exchange (RFC 8693) flow(s).

CompanyFinTechCreditCredit BuildingPaymentsCardsEmbedded FinanceBill PayBankingKYC
Methods: http, oauth2 Schemes: 3 OAuth flows: clientCredentials, token-exchange (RFC 8693) API key in:

Security Schemes

bearerAuth http
scheme: bearer
oauth2ClientCredentials oauth2
oauth2TokenExchange oauth2

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: openapi/upward-financial-openapi.json
docs: https://developers.upwardli.com/concepts/authentication/introduction
description: >-
  The Upward (Upwardli) Credit Suite API uses OAuth 2.0 for machine-to-machine
  authentication. Partners obtain a Bearer access token from the dedicated
  Authorization service (client_credentials grant with client_id +
  client_secret and requested scopes), then pass it in the Authorization
  header of every API request. A second endpoint implements RFC 8693 OAuth
  token exchange to down-scope a partner token to a single consumer
  (consumer:<upward_consumer_id>), producing a limited token that is safe to
  ship to a client application or browser. The OpenAPI declares the resulting
  Bearer scheme (http bearer).
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - clientCredentials
  - token-exchange (RFC 8693)
token_endpoints:
  sandbox: https://auth-sandbox.upwardli.com/auth/token/
  production: https://auth.upwardli.com/auth/token/
token_exchange_endpoints:
  sandbox: https://auth-sandbox.upwardli.com/auth/token/exchange/
  production: https://auth.upwardli.com/auth/token/exchange/
token_lifetimes:
  partner_access_token_seconds: 86400
  exchanged_consumer_token_seconds: 3600
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  sources:
  - openapi/upward-financial-openapi.json
- name: oauth2ClientCredentials
  type: oauth2
  flow: clientCredentials
  tokenUrl: https://auth.upwardli.com/auth/token/
  notes: >-
    Documented on the developer portal (not declared in the OpenAPI, which
    only models the resulting Bearer header). Request body is JSON with
    grant_type, client_id, client_secret, and space-separated scope.
  sources:
  - https://developers.upwardli.com/concepts/authentication/o-auth-2-0
- name: oauth2TokenExchange
  type: oauth2
  flow: token-exchange
  grant_type: urn:ietf:params:oauth:grant-type:token-exchange
  tokenUrl: https://auth.upwardli.com/auth/token/exchange/
  notes: >-
    RFC 8693 token exchange. Exchanges a partner access_token for a
    consumer-scoped token (scope consumer:<upward_consumer_id>) with a
    1-hour lifetime, safe to send to the client application.
  sources:
  - https://developers.upwardli.com/concepts/authentication/token-exchange
related:
  scopes: scopes/upward-financial-scopes.yml
  conventions: conventions/upward-financial-conventions.yml