Merge · Authentication Profile

Merge Authentication

Authentication

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

IntegrationsPlatformUnified APIAgent HandlerLLM Gateway
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

tokenAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/merge-accounting-api-openapi.yaml, openapi/merge-agent-handler-api-openapi.yaml,
  openapi/merge-ats-api-openapi.yaml, openapi/merge-chat-api-openapi.yaml, openapi/merge-crm-api-openapi.yaml,
  openapi/merge-file-storage-api-openapi.yaml, openapi/merge-hris-api-openapi.yaml, openapi/merge-knowledge-base-api-openapi.yaml,
  openapi/merge-ticketing-api-openapi.yaml
summary:
  types:
  - http
schemes:
- name: tokenAuth
  type: http
  scheme: bearer
  description: Token-based authentication with required prefix "Bearer"
  sources:
  - openapi/merge-accounting-api-openapi.yaml
  - openapi/merge-agent-handler-api-openapi.yaml
  - openapi/merge-ats-api-openapi.yaml
  - openapi/merge-chat-api-openapi.yaml
  - openapi/merge-crm-api-openapi.yaml
  - openapi/merge-file-storage-api-openapi.yaml
  - openapi/merge-hris-api-openapi.yaml
  - openapi/merge-knowledge-base-api-openapi.yaml
  - openapi/merge-ticketing-api-openapi.yaml