Agicap · Authentication Profile

Agicap Authentication

Authentication

Agicap secures its APIs with apiKey, http, and oauth2 across 5 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials and implicit flow(s).

CompanyCash ManagementTreasuryPaymentsBankingAccounts ReceivableE-InvoicingFinancial ServicesFinTechApplicative Saas
Methods: apiKey, http, oauth2 Schemes: 5 OAuth flows: clientCredentials, implicit API key in: header

Security Schemes

bearer http
scheme: bearer
bearer_client_credentials oauth2
· flows: clientCredentials
Bearer http
scheme: Bearer
OAuth2 oauth2
· flows: implicit
ApiKey apiKey
· in: header (X-API-Key)

Source

Authentication Profile

Raw ↑
generated: '2026-07-17'
method: derived
source: openapi/agicap-ar-clients-v1-openapi.json, openapi/agicap-banking-documents-v1-openapi.json,
  openapi/agicap-business-documents-v1-openapi.json, openapi/agicap-business-documents-v2-openapi.json,
  openapi/agicap-card-expenses-bank-journal-v1-openapi.json, openapi/agicap-chart-of-accounts-v1-openapi.json,
  openapi/agicap-client-risk-v1-openapi.json, openapi/agicap-einvoicing-v1-openapi.json, openapi/agicap-events-v1-openapi.json,
  openapi/agicap-financial-investments-v1-openapi.json, openapi/agicap-httpbin-v1-openapi.json,
  openapi/agicap-intragroup-financing-v1-openapi.json ...
summary:
  types:
  - apiKey
  - http
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - clientCredentials
  - implicit
schemes:
- name: bearer
  type: http
  scheme: bearer
  bearerFormat: JWT
  sources:
  - openapi/agicap-ar-clients-v1-openapi.json
  - openapi/agicap-banking-documents-v1-openapi.json
  - openapi/agicap-business-documents-v1-openapi.json
  - openapi/agicap-business-documents-v2-openapi.json
  - openapi/agicap-card-expenses-bank-journal-v1-openapi.json
  - openapi/agicap-chart-of-accounts-v1-openapi.json
  - openapi/agicap-client-risk-v1-openapi.json
  - openapi/agicap-einvoicing-v1-openapi.json
  - openapi/agicap-events-v1-openapi.json
  - openapi/agicap-financial-investments-v1-openapi.json
  - openapi/agicap-httpbin-v1-openapi.json
  - openapi/agicap-intragroup-financing-v1-openapi.json
  - openapi/agicap-invoices-management-v1-openapi.json
  - openapi/agicap-organizations-v1-openapi.json
  - openapi/agicap-payments-v2-openapi.json
  - openapi/agicap-purchase-journal-v1-openapi.json
  - openapi/agicap-suppliers-v1-openapi.json
  - openapi/agicap-treasury-bank-journal-v1-openapi.json
- name: bearer_client_credentials
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://myaccount.agicap.com/connect/token
    scopes: 1
  description: 'Client credentials: bearer'
  sources:
  - openapi/agicap-banking-documents-v1-openapi.json
  - openapi/agicap-business-documents-v1-openapi.json
  - openapi/agicap-business-documents-v2-openapi.json
  - openapi/agicap-card-expenses-bank-journal-v1-openapi.json
  - openapi/agicap-chart-of-accounts-v1-openapi.json
  - openapi/agicap-einvoicing-v1-openapi.json
  - openapi/agicap-financial-investments-v1-openapi.json
  - openapi/agicap-httpbin-v1-openapi.json
  - openapi/agicap-intragroup-financing-v1-openapi.json
  - openapi/agicap-organizations-v1-openapi.json
  - openapi/agicap-payments-v2-openapi.json
  - openapi/agicap-purchase-journal-v1-openapi.json
  - openapi/agicap-suppliers-v1-openapi.json
  - openapi/agicap-treasury-bank-journal-v1-openapi.json
- name: Bearer
  type: http
  scheme: Bearer
  sources:
  - openapi/agicap-card-expenses-bank-journal-v1-openapi.json
  - openapi/agicap-invoices-management-v1-openapi.json
  - openapi/agicap-payments-v2-openapi.json
  - openapi/agicap-purchase-journal-v1-openapi.json
- name: OAuth2
  type: oauth2
  flows:
  - flow: implicit
    authorizationUrl: https://myaccount.agicap.com/connect/authorize
    scopes: 1
  sources:
  - openapi/agicap-events-v1-openapi.json
- name: ApiKey
  type: apiKey
  in: header
  parameter: X-API-Key
  description: Used for internal API endpoints instead of bearer token
  sources:
  - openapi/agicap-payments-v2-openapi.json