Vic.ai · Authentication Profile

Vicai Authentication

Authentication

Vic.ai secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyFintechAccounts PayableInvoicingPaymentsERP IntegrationAIFinance AutomationWebhooks
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://docs.vic.ai (Authentication) + openapi/vicai-openapi-original.json
docs: https://docs.vic.ai
summary:
  types:
  - http
  http_schemes:
  - bearer
  model: client-credentials -> Bearer JWT
flow:
  token_endpoint: POST /v0/token
  request_body: '{ "client_id": "...", "client_secret": "..." }'
  response: '{ "access_token": "<JWT>", "token_type": "Bearer", "expires_in": 3600 }'
  usage: 'Authorization: Bearer <access_token>'
  ttl_seconds: 3600
  credentials_source: Issued securely by a Vic.ai representative on request (no self-service key provisioning).
  notes:
  - Access tokens are JWTs and may exceed 530 characters; storage must not impose a character limit.
  - Credentials are the keys to the ERP integration and must be kept secret.
  - Rate limiting and most authorization is scoped per OAuth client id.
schemes:
- name: BearerAuth
  type: http
  scheme: bearer
  bearer_format: JWT
  sources:
  - openapi/vicai-openapi-original.json