TawkitAI · Authentication Profile

Tawkitai Authentication

Authentication

TawkitAI secures its APIs with apiKey across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyAI AgentsCopilotsGenerative UIFrontendDeveloper ToolsReactSDKOpen SourceLLM
Methods: apiKey Schemes: 2 OAuth flows: API key in: header, config

Security Schemes

copilotCloudPublicApiKey apiKey
· in: config ()
selfHostedRuntime custom

Source

Authentication Profile

tawkitai-authentication.yml Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://docs.copilotkit.ai/auth
docs: https://docs.copilotkit.ai/auth
summary:
  types: [apiKey]
  api_key_in: [header, config]
  oauth2_flows: []
note: >-
  CopilotKit is a framework rather than a REST provider, so there is no OpenAPI
  securitySchemes block to derive from. Copilot Cloud is authenticated with a
  project API key: a public API key is supplied to the frontend <CopilotKit>
  provider (publicApiKey), and requests are routed through the hosted Copilot
  Runtime. Self-hosted deployments run their own Copilot Runtime and can layer
  arbitrary application auth in front of it.
schemes:
  - name: copilotCloudPublicApiKey
    type: apiKey
    in: config
    description: >-
      Copilot Cloud public API key passed to the frontend CopilotKit provider
      (publicApiKey prop) to connect an app to a hosted Copilot Cloud project.
    sources: [https://docs.copilotkit.ai/auth]
  - name: selfHostedRuntime
    type: custom
    description: >-
      Self-managed Copilot Runtime deployments authenticate with whatever
      application-level auth the developer places in front of the runtime
      endpoint; no CopilotKit-imposed scheme.
    sources: [https://docs.copilotkit.ai/backend/self-managed-agents]