Reference

Backend API Reference — Kaltura Agentic Avatars

Every endpoint, the full agent lifecycle, and a verified use-case catalog — copy-paste ready. This page is the index; the reference itself lives in focused files under docs/api/.

New here? Start with Getting Started. Runtime details live in Platform Overview. The zero-dependency SDK is in README.md.

Credentials — all examples need AGENTIC_PARTNER_ID and AGENTIC_ADMIN_SECRET (Rich Media CMS → Settings → Integration Settings). Set them in a local .env file, or pass them inline. To use a .env file, create it in the repo root with AGENTIC_PARTNER_ID=... and AGENTIC_ADMIN_SECRET=... on their own lines — .gitignore already excludes it. Never hardcode the secret.

Every endpoint is shown as a raw HTTP call plus its SDK wrapper. The SDK is what ships in this repo — see README.md for the full Management method list.


Contents

File Covers
Authentication & Services KS types and minting, userId binding, the five services and their base URLs
Catalog & Assets Browse the catalog, custom voice (clone), provider voice import, custom visual (portrait, photo spec), custom face/background, end-to-end portrait recipe
Agent Components Generate an agent profile, create/configure an intellect, preview a prompt, tools (api/csv/code), secrets, ground in your content (RAG), create an avatar, create an agent
Widget & Runtime Init Resolve widget ID, initialize the browser runtime
Conversation & Analytics Converse (headless HTTP), reserved sys__* template variables, status, threads, feedback and follow-ups, usage analytics, knowledge search (MCP)
Scripted-Video (STV-only) Sessions Pre-authored speech sessions — auth, lifecycle, say-audio
Management Operations CRUD tables for agents, avatars, intellects, tools, skills, threads, messages/feedback/followups, knowledge records, lifecycle
Lifecycle Rules Event-driven rules + InsightSettings (reusable custom-insight definitions) + EmailTemplates (sendInsightEmail's templateId) — reference + recipe
Use-Case Catalog All 13 use cases (UC-1 through UC-13) mapped to mechanisms and runnable scripts
Site navigation Fire-and-forget go_to tool, compact SITE MAP prompt, sections.json manifest, browser SiteNavigator plugin

Section shorthand. Docs and source comments cite sections as API-REFERENCE.md § <name> — find the section in the table above. Common ones:


What can you build? A few examples:

See the full Use-Case Catalog for all 13, each mapped to its key mechanism and a runnable script/tool.


Common Errors

The SDK wraps every error into a KalturaError with a stable err.code. Branch on that, not on prose or the raw upstream body.

Status err.code Fix
400 bad_request Fix the request body
403 forbidden Wrong KS type: admin KS for management, geniegpcid for conversations
405 method_not_allowed Use GET for /assistant/status; everything else is POST

Upstream error text is also normalized to a stable err.code, regardless of the HTTP status the backend returned it with:

Upstream detail contains err.code Fix
AGENT_NOT_FOUND agent_not_found Check the agentId
AGENT_PARTNER_CONFIG_NOT_FOUND intellect_not_found Create the intellect first

Quick Reference

The full Management method surface (this doc's endpoints, wrapped) is listed in README.md → Management. Two common lookups:

import { Management } from '@kaltura/intelligent-agents/management';
const mgmt = new Management({ partnerId, adminSecret });
const ks = await mgmt.sessions.createAdminToken();

console.log(await mgmt.agents.list(ks).all());
console.log(await mgmt.intellects.list(ks).all());
Click to talk with Nova — she knows this whole SDK.
Nova AI assistant — knows this whole site

Reloading starts a fresh chat. “New conversation” does the same without leaving the drawer.