Quenza · Authentication Profile

Quenza Authentication

Authentication

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

CoachingTherapyClient EngagementDigital HealthMental HealthPractice ManagementPositive Psychology

Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

http http

scheme: bearer

Source

Authentication Profile

generated: '2026-07-11'
method: derived
source: openapi/quenza-openapi.yml
summary:
  types:
  - http
schemes:
- name: http
  type: http
  scheme: bearer
  description: |-
    Authenticate using a **Bearer token** in the `Authorization` header:

    ```
    Authorization: Bearer {your-token}
    ```

    You can generate or regenerate your API token in your Quenza workspace under
    **Settings → Developer Tools → API Token**.
  sources:
  - openapi/quenza-openapi.yml

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/quenza-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.