Simplifi/Simplifipay · Authentication Profile

Simplifi Simplifipay Authentication

Authentication

Simplifi/Simplifipay secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyCardsCard IssuingVirtual CardsFintechPaymentsBanking as a ServiceEmbedded FinanceGCCWebhooks
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://apidoc.simplifipay.com/
docs: https://apidoc.simplifipay.com/auth.md
summary:
  types:
  - http
  http_schemes:
  - bearer
  token_format: JWT
model: 'Two-legged login: exchange client_id + client_secret (grant_type=client_credentials) at POST /v1/auth/login/{companyName}
  for a JWT access token, then send it as Authorization: Bearer <token> on every subsequent call. A separate
  SDK-admin token (POST /v1/auth/sdk/{companyName}) is minted for the Virtual Card SDK. Every request
  also requires a unique requestUuid header (20-40 chars) for traceability.'
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: JWT access token obtained from POST /v1/auth/login/{companyName}.
  token_endpoint: /v1/auth/login/{companyName}
  credentials:
  - client_id (e.g. simplifi-api-client)
  - client_secret
  - grant_type=client_credentials
  sources:
  - openapi/simplifi-simplifipay-openapi.yml
credentials_provisioning: Sandbox credentials (client_id/client_secret and companyName) are issued after
  registering at https://simplifipay.com/contact-us/.