Cinchy · Authentication Profile

Cinchy Authentication

Authentication

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

CompanyDataData CollaborationDatawareData IntegrationData GovernanceAI GovernanceAPI
Methods: http, oauth2, apiKey Schemes: 4 OAuth flows: clientCredentials API key in:

Security Schemes

bearerToken http
scheme: bearer
personalAccessToken http
scheme: bearer
basicAuth http
scheme: basic
oauth2ClientCredentials oauth2

Source

Authentication Profile

cinchy-authentication.yml Raw ↑ 
generated: '2026-07-18'
method: searched
source: https://docs.cinchy.com/api-guide/
docs: https://docs.cinchy.com/api-guide/
summary:
  types: [http, oauth2, apiKey]
  http_schemes: [bearer, basic]
  oauth2_flows: [clientCredentials]
  notes: >-
    Cinchy is a per-tenant deployed platform (self-hosted or Cinchy-hosted), so
    the base URL is tenant-specific. Authentication is served by an embedded
    IdentityServer (OAuth2/OIDC) at the /identity/connect/token endpoint.
schemes:
  - name: bearerToken
    type: http
    scheme: bearer
    description: >-
      Access token obtained from the OAuth2 token endpoint (/identity/connect/token),
      passed in the Authorization header.
  - name: personalAccessToken
    type: http
    scheme: bearer
    description: >-
      User-generated Personal Access Token (PAT) passed as a bearer token in the
      Authorization header for API access.
  - name: basicAuth
    type: http
    scheme: basic
    description: >-
      HTTP Basic authentication via the /BasicAuthAPI/ URL prefix as an alternative
      to bearer tokens.
  - name: oauth2ClientCredentials
    type: oauth2
    flow: clientCredentials
    tokenUrl: "<baseurl>/identity/connect/token"
    description: >-
      OAuth2-style token endpoint (IdentityServer) used to obtain access tokens for
      programmatic API access.