cQnce · Authentication Profile

cQnce Authentication

Authentication

cQnce secures its APIs with apiKey and http across 4 declared security schemes, as derived from its OpenAPI definitions.

CompanyHuman-in-the-LoopApprovalsAuthorizationAI AgentsMCPWebhookWorkflowsAudit
Methods: apiKey, http Schemes: 4 OAuth flows: API key in: header

Security Schemes

projectApiKey apiKey
· in: header (x-api-key)
tenantJWT http
scheme: bearer
agentJWT http
scheme: bearer
clientCredentials apiKey
· in: header (x-client-id + x-client-secret)

Source

Authentication Profile

Raw ↑ 
generated: '2026-11-04'
method: searched
source: https://cqnce.app/en/developers
docs: https://cqnce.app/en/developers
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: projectApiKey
  type: apiKey
  in: header
  parameter: x-api-key
  description: Per-project API key used for server-to-server request submission (e.g. POST /v1/requests). Docs - "Project API key (x-api-key header) for request submission endpoints such as /v1/requests."
  sources:
  - openapi/cqnce-app-openapi.yml
  - https://cqnce.app/en/developers
- name: tenantJWT
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: Tenant JWT (Bearer) for management endpoints (projects, agents, teams, routing rules), obtained via POST /v1/auth/login.
  sources:
  - openapi/cqnce-app-openapi.yml
  - https://cqnce.app/en/developers
- name: agentJWT
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: JWT issued on agent login/register (POST /v1/auth/agent/login or /register); used by the approver mobile app surface.
  sources:
  - openapi/cqnce-app-openapi.yml
- name: clientCredentials
  type: apiKey
  in: header
  parameter: x-client-id + x-client-secret
  description: Optional client credentials headers (x-client-id, x-client-secret) are also supported for request submission flows. Not declared as a securityScheme in the OpenAPI; documented on the quickstart and SDK README.
  sources:
  - https://cqnce.app/en/developers
  - https://github.com/cqnce-app/cqnce-sdk
oauth2: false
note: No OAuth 2.0 / OIDC is documented; scopes artifact not applicable. Webhook callbacks are signed with HMAC-SHA256 (X-cQnce-Signature header) and decisions with ECDSA P-256.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/cqnce-app-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.