Skip to main content
These pages describe the Training API update on codex/knowlify-training-api-updates. The update has not yet been deployed or verified end to end on a live environment. New fields, stricter edit behavior, and website brand lookup require the updated API and worker. See Testing and availability.
External integrations send an API key over HTTPS: Using an AI assistant instead of writing API requests? See Connect an AI assistant for Knowlify sign-in through MCP. That connection uses separate OAuth tokens and keeps your API key on Knowlify servers.
Generate the key in the dashboard’s Developer tab and use the API base URL shown for your environment. Keep the key on your server or in a secret manager, outside client-side code and source control. API access requires the account’s API entitlement.

​
Workspace scope

  • Personal keys can access the owner’s personal videos, not organization-linked videos.
  • Organization keys can access videos linked to that organization, subject to current membership.
  • Broader access available to the key creator in the app does not widen the key’s scope.
  • Edit polling and revert verify access to both the edit record and its underlying video.
  • Listing and job actions follow the same workspace checks. Deleted chats remove job access, so detail and action routes return 404.
For creation, omit org_id when using an API key. If supplied, it must match the key’s scope; a mismatch returns 400. A personal key cannot select an organization through the request body.

​
Supported routes

Keys authorize the Training routes listed in the API reference and the Marketing video routes supported by the deployment. Other app routes may require a first-party session. First-party clients can use Authorization: Bearer <jwt> with their authenticated session. Session access rules are separate from API-key scope; do not use app-session access as a test of a key’s permissions.

​
Failures

Missing or invalid credentials return 401. Inaccessible resources or missing entitlement can return 403. See Errors. The context.dev provider credential is configured on the API service. It is separate from your Knowlify API key and is not sent by API clients.