Convercent · Authentication Profile

Convercent Authentication

Authentication

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

CompanySaasComplianceGovernance Risk And ComplianceEthicsCase ManagementODataReporting
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

basicAuth http
scheme: basic

Source

Authentication Profile

convercent-authentication.yml Raw ↑ 
generated: '2026-07-18'
method: searched
source: https://support.convercent.com/hc/en-us/articles/205259429-Convercent-OData-
docs: https://support.convercent.com/hc/en-us/articles/205259429-Convercent-OData-
summary:
  types: [http]
  http_schemes: [basic]
  notes: >-
    The Convercent OData data-services API authenticates with HTTP Basic using a
    Convercent user name and password. Access is licensed and restricted to
    Administrators and Moderators of the respective domain; only those accounts
    can consume the OData endpoints. There is no public OAuth or API-key surface
    documented for the data API. (Application sign-in supports SAML SSO via
    identity providers such as Okta, but that governs the web app, not the API.)
schemes:
  - name: basicAuth
    type: http
    scheme: basic
    description: >-
      HTTP Basic authentication using Convercent credentials (user name +
      password). Configured in OData/BI clients by selecting "Basic" and
      entering the Convercent user name and password.
    applies_to:
      - https://api.convercent.com/OData/case/v5/CaseManagement.svc/
      - https://api.convercent.com/OData/v4/CampaignService.svc/
    sources: [docs]