Knownwell · Authentication Profile

Knownwell Authentication

Authentication

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

CompanyCommercial IntelligenceClient IntelligenceCustomer SuccessRevenue OperationsProfessional ServicesArtificial IntelligenceAnalyticsCRMChurn Risk
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

APIKeyHeader apiKey
· in: header (X-API-Key)

Source

Authentication Profile

Raw ↑
generated: '2026-07-19'
method: searched
source: openapi/knownwell-ci-openapi-original.json
docs: https://api.knownwell.com/docs#authentication
summary:
  types:
  - apiKey
  api_key_in:
  - header
  oauth2_flows: []
  read_only: true
schemes:
- name: APIKeyHeader
  type: apiKey
  in: header
  parameter: X-API-Key
  sources:
  - openapi/knownwell-ci-openapi-original.json
  docs: https://api.knownwell.com/docs#authentication
  description: 'The Knownwell API uses API key authentication via HTTP headers. Include your
    API key in the X-API-Key header with every request. Requests without proper authentication
    return a 401 Unauthorized error.'
key_management:
  issuance: 'Generate an API key from Integrations > API Connector in the Knownwell dashboard
    (https://ci.knownwell.com/).'
  scope: read_only
  scope_note: 'The OpenAPI APIKeyScope enum has a single value, read_only, documented as "API
    key access scope - ALL KEYS ARE READ-ONLY". No write, update, or delete operations are
    permitted with an API key.'
  key_scoped_to: customer_id
  expiration: 'Optional. API keys may be created with expires_days; omitting it creates a
    non-expiring key (openapi APIKeyCreate.expires_days).'
  management_operations:
  - create_api_key_v1_api_keys_post
  - list_api_keys_v1_api_keys_get
  - revoke_api_key_v1_api_keys__key_id__delete
best_practices:
- Never expose your API key in client-side code or public repositories
- Store securely in environment variables or secure vaults
- Rotate regularly — request new keys periodically
- Use HTTPS only — all API calls must use HTTPS
- Monitor usage — track API usage for unauthorized access
example: |
  curl https://api.knownwell.com/ci/v1/clients \
    -H "X-API-Key: your_api_key_here"
notes:
- No OAuth 2.0 or OpenID Connect surface is published; scopes/ is therefore not applicable.

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/knownwell-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 email required.

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