# Kaltura Documentation

> APIs, SDKs, MCP, and AI Skills for the Agentic Digital Experience Platform

## Getting Started

> **Authentication**: Kaltura Sessions (KS) and App Tokens — authentication for all API integrations.

> **Getting Started**: Obtain credentials, understand the API surface, and orient yourself across Kaltura's developer platform.

- [Overview](https://docs.kaltura.com/docs/getting-started/authentication/ks-overview.md): What a KS is, when to use each session flow, and prerequisites.
- [KS Fundamentals](https://docs.kaltura.com/docs/getting-started/authentication/ks-fundamentals.md): KS internal structure, validation flow, and creation method comparison.
- [Security Practices](https://docs.kaltura.com/docs/getting-started/authentication/ks-security.md): Least privilege, short TTLs, backend-only secrets, and entitlements.
- [REST API Recipes](https://docs.kaltura.com/docs/getting-started/authentication/ks-api-recipes.md): Generate a KS with session.start, bootstrap with startWidgetSession, and AppToken exchange.
- [Passing the KS](https://docs.kaltura.com/docs/getting-started/authentication/ks-usage.md): How to pass KS to API calls and player embeds.
- [Privileges](https://docs.kaltura.com/docs/getting-started/authentication/ks-privileges.md): Privilege strings, entitlements, privacy context, hardening knobs, and copy/paste sets.
- [Renewal & Caching](https://docs.kaltura.com/docs/getting-started/authentication/ks-renewal.md): TTL management, client patterns, session revocation, and caching.
- [Error Handling](https://docs.kaltura.com/docs/getting-started/authentication/ks-error-handling.md): KS-related error codes, retry strategy, and observability.
- [Best Practices](https://docs.kaltura.com/docs/getting-started/authentication/ks-best-practices.md): Production KS patterns, mobile/client-side strategies, and related guides.
- [Overview](https://docs.kaltura.com/docs/getting-started/authentication/app-tokens-overview.md): What AppTokens are, when to use them, and prerequisites.
- [Why AppTokens](https://docs.kaltura.com/docs/getting-started/authentication/app-tokens-why.md): AppTokens vs admin secrets — revocation, scoping, rotation, and audit comparison.
- [AppToken Object](https://docs.kaltura.com/docs/getting-started/authentication/app-tokens-object.md): KalturaAppToken fields, status values, and locked-at-creation properties.
- [CRUD Operations](https://docs.kaltura.com/docs/getting-started/authentication/app-tokens-crud.md): Add, get, list, update, and delete AppTokens with curl examples.
- [HMAC Session Flow](https://docs.kaltura.com/docs/getting-started/authentication/app-tokens-hmac-flow.md): Three-step widget session + HMAC hash + startSession exchange.
- [Privilege Reference](https://docs.kaltura.com/docs/getting-started/authentication/app-tokens-privileges.md): Access control and session control privileges with common privilege sets.
- [Token Rotation](https://docs.kaltura.com/docs/getting-started/authentication/app-tokens-rotation.md): Zero-downtime token rotation pattern.
- [Hash Types](https://docs.kaltura.com/docs/getting-started/authentication/app-tokens-hash-types.md): MD5, SHA1, SHA256, SHA512 — security levels and recommendations.
- [Error Handling](https://docs.kaltura.com/docs/getting-started/authentication/app-tokens-error-handling.md): AppToken-specific error codes and retry strategy.
- [Best Practices](https://docs.kaltura.com/docs/getting-started/authentication/app-tokens-best-practices.md): Hash choice, privilege scoping, token rotation, server-side storage, and related guides.
- [Overview](https://docs.kaltura.com/docs/getting-started/general/api-overview.md): API surface overview, when to use, and prerequisites for getting started.
- [API Request Structure](https://docs.kaltura.com/docs/getting-started/general/api-request-structure.md): HTTP method, content types, parameter encoding, objectType, and request patterns.
- [Endpoints & Regions](https://docs.kaltura.com/docs/getting-started/general/api-endpoints-regions.md): Regional API base URLs, URL naming conventions, service endpoints, and protocols.
- [Content Model](https://docs.kaltura.com/docs/getting-started/general/api-content-model.md): Entries, assets, entry lifecycle, and partial update semantics.
- [Your First API Call](https://docs.kaltura.com/docs/getting-started/general/api-first-call.md): Generate a KS and list media entries with curl.
- [Client Libraries](https://docs.kaltura.com/docs/getting-started/general/api-client-libraries.md): Official client libraries for JavaScript, Python, PHP, Java, and more.
- [Multirequest](https://docs.kaltura.com/docs/getting-started/general/api-multirequest.md): Batch multiple API calls into a single HTTP request with result chaining.
- [Shell Variables](https://docs.kaltura.com/docs/getting-started/general/api-shell-variables.md): Standard shell variables used across all curl examples in these guides.
- [Error Handling](https://docs.kaltura.com/docs/getting-started/general/api-error-handling.md): Error response format, common error codes, and retry strategy.
- [Best Practices](https://docs.kaltura.com/docs/getting-started/general/api-best-practices.md): Production authentication, response format, regional endpoints, and session management tips.
- [Overview](https://docs.kaltura.com/docs/getting-started/general/credentials-overview.md): When to use this guide, how to get a Kaltura account, and what credentials you need.
- [Find Your Credentials](https://docs.kaltura.com/docs/getting-started/general/credentials-find.md): Locate your Partner ID, Admin Secret, Service URL, Player ID, User ID, and Video Portal URL.
- [Configure Your Environment](https://docs.kaltura.com/docs/getting-started/general/credentials-environment.md): Set up .env file and shell variables for API examples.
- [Verify Your Credentials](https://docs.kaltura.com/docs/getting-started/general/credentials-verify.md): Generate a KS and confirm your credentials work with a test API call.
- [Credential Reference](https://docs.kaltura.com/docs/getting-started/general/credentials-reference.md): Summary table of all credential variables, formats, and sources.
- [Error Handling](https://docs.kaltura.com/docs/getting-started/general/credentials-error-handling.md): Common credential-related error codes and resolutions.
- [Best Practices](https://docs.kaltura.com/docs/getting-started/general/credentials-best-practices.md): AppTokens for production, secret management, short-lived sessions, and KS types.

## Agents & Avatars

> **Agentic Avatars SDK**: Client SDK and Control API for real-time interactive avatar sessions — setup, messaging, state, and teardown.

> **Avatar Videos**: Create pre-recorded avatar video presentations programmatically — scene scripting, AI composition, and generation.

> **Conversational Agents**: Management APIs for configuring avatar visuals, voices, AI personalities, knowledge bases, and conversational agents on the Kaltura platform.

- [Prerequisites](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/prerequisites.md): Required Kaltura Session credentials, Node.js version, and account setup before integrating avatars.
- [Choosing Your Approach](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/choosing-approach.md): Compare SDK-based client-side control vs. API-based server-side control for avatar sessions.
- [SDK Quick Start](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/quick-start-sdk.md): Get a working avatar running in 5 minutes using client-side SDK control for demos and prototypes.
- [API Quick Start](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/quick-start-api.md): Production-ready setup using server-side API control with secure Kaltura Session handling.
- [Installation](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/client-sdk-installation.md): Install the @unisphere/models-sdk-js package via npm or yarn with TypeScript support.
- [Basic Usage](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/client-sdk-basic-usage.md): Create a KalturaAvatarSession instance, connect to an avatar, and control it with the SDK.
- [API Reference](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/client-sdk-api-reference.md): Complete reference for KalturaAvatarSession constructor, methods, properties, events, and types.
- [State Management](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/client-sdk-state-management.md): Track and respond to avatar session states (IDLE, CREATING, READY, ENDED) and connection events.
- [Error Handling](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/client-sdk-error-handling.md): AvatarError types, error codes, and strategies for handling SDK errors gracefully.
- [Advanced Usage](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/client-sdk-advanced.md): Advanced SDK topics: apiKey usage patterns, backend/frontend session split, and custom configuration.
- [Overview](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/control-api-overview.md): Introduction to the server-side REST Control API for secure, scalable avatar session management.
- [Authentication](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/control-api-authentication.md): Authenticate Control API requests using Kaltura Sessions for creation and JWT tokens for control.
- [Create Session](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/control-api-create-session.md): POST endpoint to create a new avatar session with visual and voice configuration.
- [Initialize Client](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/control-api-init-client.md): POST endpoint to initialize the avatar client and retrieve WebRTC connection configuration.
- [Say Text](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/control-api-say-text.md): POST endpoint to make the avatar speak provided text using text-to-speech.
- [Say Audio](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/control-api-say-audio.md): POST endpoint to make the avatar lip-sync and speak from an uploaded audio file.
- [Interrupt](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/control-api-interrupt.md): POST endpoint to interrupt the avatar's current speech or action mid-stream.
- [Keep Alive](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/control-api-keep-alive.md): POST endpoint to prevent an idle avatar session from timing out.
- [End Session](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/control-api-end-session.md): POST endpoint to end an avatar session and release its server-side resources.
- [API Examples](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/control-api-examples.md): Complete code examples showing the full Control API flow from session creation to teardown.
- [Catalog Service](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/client-sdk-catalog.md): Query available avatar visuals and voices programmatically using the CatalogService class.
- [Simple Client-Side Example](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/examples-simple-client-side.md): Full HTML and JavaScript example of SDK-based avatar control for demos and prototypes.
- [Server Controlled Example](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/examples-server-controlled.md): Production-ready Express and React example with backend API control and frontend display.
- [React Integration](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/examples-react-integration.md): Custom useAvatar hook and React components for integrating Kaltura Avatar into a React app.
- [Error Recovery](https://docs.kaltura.com/docs/conversational-agents/agentic-avatars-sdk/examples-error-recovery.md): Retry patterns with exponential backoff and graceful error recovery for avatar sessions.
- [Avatar Videos](https://docs.kaltura.com/docs/conversational-agents/avatar-videos.md): Overview of the VOD Avatar Studio API — integration paths, base URLs, and authentication.
- [When to Use](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/when-to-use.md): Use cases for the VOD Avatar API — training videos, localization, executive comms, session highlights, and automated pipelines.
- [Prerequisites](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/prerequisites.md): Required Kaltura Session, account provisioning, and caption requirements before using the VOD Avatar API.
- [Architecture](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/architecture.md): Two-layer architecture (server-side API and embeddable widget), API flow, and video status lifecycle.
- [Auth & Headers](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/auth.md): Authentication with Kaltura Session (KS), required headers, and partner configuration checks.
- [Avatar Templates & Configuration](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/avatar-templates.md): List available AI presenter templates and create reusable avatar configurations with backgrounds.
- [Video Project Management](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/video-management.md): Create, update, list, and delete video projects — scenes, narration, layout types, and b-roll configuration.
- [AI Composition](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/ai-composition.md): Use AI to generate scene narration from source video captions — session highlights and video explainers.
- [Audio Preview](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/audio-preview.md): Preview text-to-speech narration for individual scenes before generating the full video.
- [Video Generation](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/video-generation.md): Generate the final video, poll for completion, diagnose errors, and reset status after failures.
- [Complete Server-Side Workflow](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/complete-workflow.md): End-to-end examples — basic workflow and manual multi-source b-roll storyboard with polling.
- [Widget Embedding](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/widget-embedding.md): Drop-in browser UI via the Kaltura embeds framework — embed code, runtime settings, project types, callbacks, and lifecycle.
- [Error Handling](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/error-handling.md): Server-side API error codes and widget troubleshooting — resolution steps for each error.
- [Best Practices](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/best-practices.md): Production guidelines — KS management, narration budgeting, b-roll preparation, and multi-region CDN endpoints.
- [Related Guides](https://docs.kaltura.com/docs/conversational-agents/avatar-videos/related-guides.md): Links to related Kaltura APIs — Conversational Avatar, Embeds Framework, REACH, Content Lab, Sessions, and AppTokens.
- [Home](https://docs.kaltura.com/docs/conversational-agents/conversational-agents.md): Overview of the Conversational Agents APIs — services, routing conventions, pagination, and how the building blocks fit together.
- [Getting Started](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/getting-started.md): Quick start guide to set up your first conversational agent in under 15 minutes.
- [Authentication](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/authentication.md): Kaltura Session (KS) authentication for all Conversational Agent management APIs.
- [Catalog Service](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/catalog-service.md): Manage visual appearances and voice catalog items — browse, upload, update, and delete.
- [Avatar Service](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/avatar-service.md): Create and configure avatars by combining a visual and voice from the catalog.
- [Intellect Service](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/intellect-service.md): Configure AI personality, prompts, glossary, knowledge base attachment, and capabilities.
- [Knowledge Service](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/knowledge-service.md): Create indexed content collections from Kaltura media or web URLs for AI search.
- [Agent Service](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/agent-service.md): Create and manage conversational agents combining avatars with intelligence engines.
- [Workflow](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/workflow.md): End-to-end workflow walkthroughs — from zero to talking avatar, makeovers, and A/B testing.
- [Embed Templates](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/embed-templates.md): Overview of all embed templates — Chat and Avatar mounting strategies.
- [Chat & Avatar Contained](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/embed-chat-contained.md): Mount the chat & avatar into any DOM element — panels, modals, or sidebars — with contained scroll.
- [Chat & Avatar Page](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/embed-chat-page.md): Full-page chat & avatar embed that scrolls within the host page context.
- [Chat & Avatar Floater](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/embed-chat-floater.md): Floating chat & avatar button anchored to a viewport corner with configurable position and behavior.
- [Avatar Head Floater](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/embed-avatar-head-floater.md): Draggable floating avatar head that auto-connects to the AI agent on mount.
- [Avatar Floater](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/embed-avatar-floater.md): Button anchored to the viewport that opens the avatar in a side panel.
- [Avatar Contained](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/embed-avatar-contained.md): Mount the avatar into a specific DOM element — panels, modals, or inline sections.
- [Avatar Headless](https://docs.kaltura.com/docs/conversational-agents/conversational-agents/embed-avatar-headless.md): Mount the avatar runtime without built-in UI for fully custom rendering.

## Rich Media CMS APIs

> **Analytics**: Pull analytics data — content performance, viewer engagement, event attendance, and operational metrics.

> **Content Management**: APIs for content lifecycle management — upload, ingest, edit, deliver, search, organize, and secure media content.

> **Content Moderation**: Manual moderation queues and AI-powered content screening — flagging, approval workflows, and automated policy evaluation.

> **Integration**: Webhooks and event notifications — HTTP callbacks triggered by platform events like uploads, transcoding, and metadata changes.

- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-overview.md): When to use analytics APIs, prerequisites, authentication, and services covered.
- [Report Response Format](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-response-format.md): Pipe-delimited table, totals, and graph response formats with parsing patterns.
- [report.getTable](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-get-table.md): Tabular analytics with pagination — filter by entry, category, or virtual event.
- [report.getTotal](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-get-total.md): Aggregate totals for a report type as a single row.
- [report.getGraphs](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-get-graphs.md): Time-series data for charting with configurable interval granularity.
- [Multi-Request Batching](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-multi-request.md): Combine getTotal, getGraphs, and getTable in a single KalturaMultiRequest call.
- [CSV Exports](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-csv-exports.md): Generate downloadable CSV exports and specialized string-parameter reports.
- [Reports Microservice](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-reports-microservice.md): Async report generation for registration, C&C, and enriched analytics data.
- [Live Analytics](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-live.md): Real-time live stream analytics — viewer counts, stream health beacons, and realtime report types.
- [Report Types Reference](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-report-types.md): KalturaReportType integer IDs for VOD, webcast, events platform, and multi-account reports.
- [Filter Fields Reference](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-filter-fields.md): KalturaEndUserReportInputFilter fields — entry, category, geography, device, user, and event filters.
- [Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-best-practices.md): Date handling, response parsing, dashboard patterns, and common integration workflows.
- [Reference](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-reference.md): Error handling, analytics permissions, and related guides.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-events-overview.md): When to use event collection APIs, prerequisites, and authentication for analytics event reporting.
- [Player Event Types](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-events-player-event-types.md): Core playback, quartile progress, quality, and engagement events fired by Kaltura Player v7.
- [stats.collect](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-events-stats-collect.md): Server-side event collection via stats.collect — event type IDs, required fields, and full session example.
- [analytics.trackEvent](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-events-track-event.md): Application-level tracking for page loads and button clicks via the analytics.trackEvent endpoint.
- [Event Reporting Protocol](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-events-reporting-protocol.md): Session management, event ordering, quartile calculation, and batching rules for analytics events.
- [Server-Side Collection](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-events-server-side.md): Report playback events from backend systems — kiosks, set-top boxes, digital signage, and batch processing.
- [Custom Event Context](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-events-custom-context.md): Per-application segmentation via appId KS privilege and event context fields.
- [Verification](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-events-verification.md): Analytics propagation delays and how to verify event delivery via report.getTable.
- [Reference](https://docs.kaltura.com/docs/rich-media-cms-apis/analytics/analytics-events-reference.md): Error handling, retry logic, best practices, and common integration patterns for analytics events.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/upload-ingestion-overview.md): This guide covers the complete lifecycle of getting content into Kaltura: creating upload tokens, uploading files (including chunked/resumable transfers), creating media, document, and data entries...
- [Upload Lifecycle Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/upload-ingestion-upload-lifecycle-overview.md): Every file upload follows this pattern:
- [Upload Token API](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/upload-ingestion-upload-token-api.md): The `uploadToken` service manages server-side containers for receiving file data. Tokens support single-shot uploads, chunked uploads with parallel transfers, and auto-finalization.
- [Creating Media Entries](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/upload-ingestion-creating-media-entries.md): Response: `KalturaMediaEntry` with `id`, `status` (7 = NO_CONTENT until file attached)
- [Entry CRUD Operations](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/upload-ingestion-entry-crud-operations.md): Poll for READY status after upload: After calling `media.addContent`, poll `media.get` until `status` reaches `2` (READY):
- [Cross-Type Entry Operations (baseEntry)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/upload-ingestion-cross-type-entry-operations-baseentry.md): The `baseEntry` service provides operations that work across all entry types (media, document, data).
- [Non-Media Entry Types](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/upload-ingestion-non-media-entry-types.md): Upload documents (PDF, DOCX, PPTX) using the `documents` service. Documents go through Kaltura's document conversion pipeline for web viewing.
- [Flavor Assets (Transcoded Renditions)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/upload-ingestion-flavor-assets-transcoded-renditions.md): A 'flavor' is a transcoded rendition of the source file (e.g., 360p, 720p, 1080p). Kaltura automatically creates flavors based on the account's conversion profile.
- [Attachment Assets (Non-Media File Attachments)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/upload-ingestion-attachment-assets-non-media-file-attachments.md): The `attachment_attachmentAsset` service attaches supplementary files to media entries (shown as 'Related Files' in KMC).
- [Bulk Upload](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/upload-ingestion-bulk-upload.md): For ingesting many files at once, use CSV or XML bulk upload.
- [Complete Example -- Chunked Upload Workflow](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/upload-ingestion-complete-example-chunked-upload-workflow.md): Resume after failure: Call `uploadToken.get` to check `uploadedFileSize`, then resume from that byte offset.
- [Error Handling & Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/upload-ingestion-reference.md): Error codes, retry strategies, and best practices for Upload & Ingestion.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-overview.md): This guide covers all non-destructive video composition operations: trimming, clipping, multi-clip concatenation, overlays (picture-in-picture), background replacement (chroma key), caption burn-in...
- [Core Concepts](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-core-concepts.md): Trimming uses `media.updateContent` which triggers the replacement flow — a safe, non-destructive update pipeline:
- [Trim (In-Place Content Replacement)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-trim-in-place-content-replacement.md): Trim shortens a video without changing its entry ID, embed codes, or analytics history.
- [Clip (Extract Segment to New Entry)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-clip-extract-segment-to-new-entry.md): Create a new entry containing a segment from an existing video.
- [Multi-Clip Concatenation](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-multi-clip-concatenation.md): Splice segments from multiple source entries into a single output.
- [Overlay (Picture-in-Picture)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-overlay-picture-in-picture.md): Compose one video on top of another at a specified position, size, and shape.
- [Background Replacement (Chroma Key)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-background-replacement-chroma-key.md): Remove a solid-color background from the foreground video and replace it with another video or image.
- [Nested Composition (Overlay + Background Replacement)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-nested-composition-overlay-background-replacement.md): The most advanced composition pattern: an avatar video recorded on green screen, with the green replaced by a custom background, then overlaid on a main B-roll video.
- [Caption Burn-In](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-caption-burn-in.md): Render caption text permanently into the video frame. Useful for social media distribution where players may not support subtitle tracks.
- [Effects (Fade In/Out)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-effects-fade-inout.md): Apply video fade transitions to clips.
- [Dimension Control](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-dimension-control.md): Control output resolution when composing or concatenating sources with different dimensions.
- [Audio Mixing](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-audio-mixing.md): Audio from overlay and background replacement sources mixes with the main video using a complementary volume model.
- [Waveform Visualization](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-waveform-visualization.md): Retrieve audio amplitude data for building visual waveform displays (useful for editing UIs).
- [Error Handling & Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/video-editing-reference.md): Error codes, retry strategies, and best practices for Video Editing.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/content-delivery-overview.md): This guide covers delivering content to viewers: constructing playManifest URLs for adaptive streaming (HLS/DASH), raw serve URLs for direct file access, download URLs, flavor asset selection, deli...
- [playManifest — Adaptive Streaming](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/content-delivery-playmanifest-adaptive-streaming.md): The `playManifest` endpoint is the primary way to get playback URLs for video and audio entries. It returns streaming manifests (HLS, DASH) or redirects to direct file URLs.
- [Raw Serve URL — Direct File Access](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/content-delivery-raw-serve-url-direct-file-access.md): The `raw` URL serves the original source file for any entry type — documents, data entries, images, SVGs, videos, or audio. Unlike `playManifest` (which returns adaptive streaming manifests) or the...
- [Download Endpoint](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/content-delivery-download-endpoint.md): The `download` endpoint serves files with `Content-Disposition: attachment` headers. It supports flavor selection and access control preview limits.
- [Flavor Asset Delivery](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/content-delivery-flavor-asset-delivery.md): The `flavorAsset` service provides API-based URL generation for specific renditions.
- [Delivery Profiles](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/content-delivery-delivery-profiles.md): Delivery profiles configure how URLs are constructed for specific CDN providers. Each profile defines the CDN host, URL pattern, and authentication/tokenization.
- [CDN URL Tokenization](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/content-delivery-cdn-url-tokenization.md): When a delivery profile has a URL tokenizer configured, signed tokens are automatically appended to all URLs in the manifest. This prevents unauthorized hotlinking.
- [Access Control on Delivery](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/content-delivery-access-control-on-delivery.md): Access control profiles define rules that are enforced server-side on every playManifest, raw, download, and thumbnail request. Rules can restrict access by IP address, country, domain, user agent,...
- [Complete Delivery Workflow](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/content-delivery-complete-delivery-workflow.md): Complete Delivery Workflow for Content Delivery.
- [Error Handling & Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/content-delivery-reference.md): Error codes, retry strategies, and best practices for Content Delivery.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/thumbnail-overview.md): This guide covers generating and managing thumbnails and images: the URL-based dynamic thumbnail API (31 parameters for on-the-fly resizing, cropping, format conversion, video frame extraction, and...
- [Dynamic Thumbnail API (URL-Based)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/thumbnail-dynamic-thumbnail-api-url-based.md): Generate thumbnails on the fly via URL parameters. Results are CDN-cached (1 hour for ready entries, 30 days in memcache) — use freely for responsive UIs and per-request customization.
- [thumbAsset API (Stored Thumbnails)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/thumbnail-thumbasset-api-stored-thumbnails.md): The `thumbAsset` service manages persistent, editorial thumbnails attached to entries. Use when you need multiple thumbnails per entry, custom-uploaded images, or saved video frame captures.
- [thumbParams API (Thumbnail Templates)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/thumbnail-thumbparams-api-thumbnail-templates.md): The `thumbParams` service defines reusable thumbnail generation specifications that can be associated with conversion profiles for automatic thumbnail generation on upload.
- [When to Use Which](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/thumbnail-when-to-use-which.md): When to Use Which for Thumbnail API.
- [Error Handling & Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/thumbnail-reference.md): Error codes, retry strategies, and best practices for Thumbnail API.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/esearch-overview.md): Kaltura's eSearch API, powered by Elasticsearch, provides flexible full-text search across media entries, categories, users, captions, custom metadata, cue points, and more — all in a single API call.
- [API Endpoint & Structure](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/esearch-api-endpoint-structure.md): * Service: `elasticsearch_esearch`
- [Core Request Parameters & Objects](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/esearch-core-request-parameters-objects.md): Requests are built using specific Kaltura objects passed as form parameters.
- [Search Item (`searchItems`) Deep Dive](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/esearch-search-item-searchitems-deep-dive.md): These objects define *what* you're searching for within the `searchOperator.searchItems` array.
- [API Response Format (JSON)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/esearch-api-response-format-json.md): The API typically returns a JSON object structured as follows:
- [Capabilities & Scenarios (with Curl Examples)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/esearch-capabilities-scenarios-with-curl-examples.md): Examples pipe to `jq` for readability.
- [Advanced Topics & Use Cases](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/esearch-advanced-topics-use-cases.md): * Aggregations (`searchParams[aggregations]`):
- [Advanced Patterns & Edge Cases](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/esearch-advanced-patterns-edge-cases.md): * 10,000 Result Limit: Elasticsearch enforces a 10K result cap (500/page x 20 pages max). To traverse larger result sets, use `KalturaESearchRange` on `created_at` with scroll-forward pagination — ...
- [Key Objects & Enums Quick Reference](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/esearch-key-objects-enums-quick-reference.md): * Params: `KalturaESearchEntryParams`, `KalturaESearchCategoryParams`, `KalturaESearchUserParams`
- [Agent / LLM Integration Notes](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/esearch-agent-llm-integration-notes.md): When exposing eSearch to an LLM via agent tools:
- [Error Handling & Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/esearch-reference.md): Error codes, retry strategies, and best practices for eSearch.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/access-control-overview.md): The Access Control API manages content access restrictions through profiles, rules, conditions, and actions. Access control profiles are assigned to entries and enforced server-side on every playMa...
- [Access Control Model](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/access-control-access-control-model.md): An access control profile (`KalturaAccessControlProfile`) contains an ordered array of rules (`KalturaRule`). Each rule has:
- [KalturaAccessControlProfile Object](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/access-control-kalturaaccesscontrolprofile-object.md): KalturaAccessControlProfile Object for Access Control.
- [Profile CRUD](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/access-control-profile-crud.md): Parameters for `accessControlProfile[...]`:
- [Rule Conditions](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/access-control-rule-conditions.md): All conditions support a `not` boolean field -- when `true`, the condition matches when the test FAILS (logical negation).
- [Rule Actions](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/access-control-rule-actions.md): Preview action (paywall):
- [Access Control Contexts](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/access-control-access-control-contexts.md): Rules are evaluated based on the delivery context:
- [Scheduling vs Access Control](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/access-control-scheduling-vs-access-control.md): Kaltura has two mechanisms for enforcing time-based access:
- [Assigning Profiles to Entries](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/access-control-assigning-profiles-to-entries.md): Assign an access control profile to an entry via `media.update` (or `baseEntry.update`):
- [Business Scenarios](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/access-control-business-scenarios.md): A sports broadcaster restricts live event playback to viewers in licensed countries. Create a profile with a country condition that blocks playback outside US and Canada, applied to the PLAY contex...
- [Error Handling & Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/access-control-reference.md): Error codes, retry strategies, and best practices for Access Control.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/categories-overview.md): The Categories & Entitlements API covers content organization and user-based content permissions: creating category hierarchies (`KalturaCategory`), managing category membership (`categoryUser`), a...
- [KalturaCategory Object](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/categories-kalturacategory-object.md): Every category in a Kaltura partner account is a `KalturaCategory`:
- [Category CRUD](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/categories-category-crud.md): Response:
- [Category Hierarchy](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/categories-category-hierarchy.md): Categories form a tree structure via the `parentId` field. The API automatically computes path fields:
- [Category Membership (categoryUser)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/categories-category-membership-categoryuser.md): Category membership controls which users belong to a category. When entitlement is enabled, membership determines who can see content assigned to `MEMBERS_ONLY` categories.
- [Content Assignment (categoryEntry)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/categories-content-assignment-categoryentry.md): Assign media entries to categories to organize content and enforce entitlement rules.
- [Entitlement System](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/categories-entitlement-system.md): Entitlement is Kaltura's mechanism for restricting content visibility based on category membership. It combines category privacy settings, user membership, and KS privileges.
- [Bulk Operations](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/categories-bulk-operations.md): Use bulk upload actions to create categories, assign members, or assign entries in batch via CSV.
- [Error Handling & Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/categories-reference.md): Error codes, retry strategies, and best practices for Categories & Entitlements.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/custom-metadata-overview.md): The Custom Metadata API lets you define XSD-based schemas (metadata profiles) and attach structured XML data to entries, categories, users, partners, or user-entry records. Schemas support typed fi...
- [Metadata Profiles (Schemas)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/custom-metadata-metadata-profiles-schemas.md): A `KalturaMetadataProfile` defines a schema (XSD) that describes the structure of custom metadata. You create a profile once, then attach metadata instances conforming to that schema to individual ...
- [XSD Schema Design](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/custom-metadata-xsd-schema-design.md): Every Kaltura metadata XSD must include four base type definitions that the KMC and eSearch use for field type detection. Fields annotated with `<appinfo>` elements control how the KMC renders the ...
- [Metadata Instances (CRUD)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/custom-metadata-metadata-instances-crud.md): A `KalturaMetadata` instance holds the actual XML data conforming to a metadata profile's XSD schema, attached to a specific object. Each object can have at most one metadata instance per profile.
- [XSLT Transformation Pipeline](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/custom-metadata-xslt-transformation-pipeline.md): Kaltura supports two XSLT mechanisms for transforming metadata XML automatically.
- [Metadata on Different Object Types](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/custom-metadata-metadata-on-different-object-types.md): The most common type. Attach custom fields to media entries for classification, workflow tracking, and searchability via eSearch.
- [Search Integration](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/custom-metadata-search-integration.md): Use `KalturaESearchEntryMetadataItem` to search entries by metadata field values:
- [Metadata in Distribution (MRSS)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/custom-metadata-metadata-in-distribution-mrss.md): When entries with custom metadata are distributed via MRSS feeds, the `kMetadataMrssManager` decorates each item with `<customData>` elements:
- [Common Integration Patterns](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/custom-metadata-common-integration-patterns.md): Check if metadata exists for an object, then add or update accordingly:
- [Business Use Cases](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/custom-metadata-business-use-cases.md): Define Department, ContentType, Region, and BusinessUnit as enum fields. Use eSearch to filter entries by department. MediaSpace uses these fields for browsing and category pages. Automation Manage...
- [Error Handling & Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/custom-metadata-reference.md): Error codes, retry strategies, and best practices for Custom Metadata.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/captions-overview.md): The Captions & Transcripts API manages subtitle files, closed captions, and transcripts attached to media entries. It supports five caption formats (SRT, DFXP/TTML, WebVTT, CAP, SCC), on-the-fly fo...
- [Caption Formats](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/captions-caption-formats.md): Timing format: `HH:MM:SS,mmm --> HH:MM:SS,mmm`. Supports `<b>`, `<i>`, `<u>` HTML tags. Blank line separates cues.
- [Caption Asset CRUD](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/captions-caption-asset-crud.md): A `KalturaCaptionAsset` represents a subtitle or caption file attached to a media entry. Caption creation is a two-step process: first create the asset metadata (`captionAsset.add`), then upload th...
- [Serving Captions](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/captions-serving-captions.md): Returns the caption content in its original format (SRT, DFXP, etc.):
- [Caption Parameters (Templates)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/captions-caption-parameters-templates.md): Caption parameter templates define reusable presets for caption assets. When `captionAsset.add` includes a `captionParamsId`, language and label are auto-copied from the template.
- [Transcripts](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/captions-transcripts.md): In practice, REACH-generated captions serve as both: the timed segments display as subtitles, and the full text is available for search and download.
- [Multi-Language Workflows](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/captions-multi-language-workflows.md): Each entry supports multiple caption tracks — one asset per language per entry. The player displays a language selector when multiple tracks exist:
- [Caption Search](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/captions-caption-search.md): Search within caption text across entries:
- [Player Integration](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/captions-player-integration.md): Kaltura Player v7 requests captions via the HLS segmented delivery flow:
- [Auto-Captioning & Automation](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/captions-auto-captioning-automation.md): REACH can auto-order captioning tasks based on triggers:
- [Accessibility Compliance](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/captions-accessibility-compliance.md): FCC caption quality requirements:
- [Business Use Cases](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/captions-business-use-cases.md): Upload lecture recording → REACH ASR auto-rule triggers → captions attached → embed in LMS. Students get searchable, captioned content within minutes of upload.
- [Error Handling & Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/captions-reference.md): Error codes, retry strategies, and best practices for Captions & Transcripts.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/multi-stream-overview.md): Create synchronized multi-stream entries for dual-screen playback — Picture-in-Picture, Side-by-Side, and stream selection. A multi-stream entry consists of a parent entry (primary video with audio...
- [Multi-Stream Architecture](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/multi-stream-multi-stream-architecture.md): A multi-stream entry is a parent-child relationship between regular media entries:
- [Create a Multi-Stream Entry Set](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/multi-stream-create-a-multi-stream-entry-set.md): This workflow creates a parent entry and links child entries to it. For the upload steps (`uploadToken.add`, `uploadToken.upload`, `media.add`, `media.addContent`), see the Upload & Ingestion Guide...
- [Link an Existing Entry as a Child](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/multi-stream-link-an-existing-entry-as-a-child.md): If you already have both videos as independent entries, link them after the fact using `baseEntry.update`:
- [Verify and List Multi-Stream Entries](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/multi-stream-verify-and-list-multi-stream-entries.md): Confirm:
- [Player v7 Dual Screen Setup](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/multi-stream-player-v7-dual-screen-setup.md): The Dual Screen plugin (`@playkit-js/playkit-js-dual-screen`) enables synchronized multi-stream playback in Kaltura Player v7 (PlayKit). It requires the `kalturaCuepoints` plugin if showing slides.
- [Playback Behavior](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/multi-stream-playback-behavior.md): Playback Behavior for Multi-Stream.
- [Complete Example — Multi-Stream Lifecycle](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/multi-stream-complete-example-multi-stream-lifecycle.md): Complete Example — Multi-Stream Lifecycle for Multi-Stream.
- [API Reference](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/multi-stream-api-reference.md): API Reference for Multi-Stream.
- [Error Handling & Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/multi-stream-reference.md): Error codes, retry strategies, and best practices for Multi-Stream.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/user-management-overview.md): The User Management API covers the core user identity layer: creating and managing users (`KalturaUser`), assigning roles for RBAC (`KalturaUserRole`), and managing group membership (`groupUser`). ...
- [KalturaUser Object](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/user-management-kalturauser-object.md): Every user in a Kaltura partner account is a `KalturaUser`:
- [User Provisioning Pathways](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/user-management-user-provisioning-pathways.md): Users are created through several pathways:
- [User CRUD](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/user-management-user-crud.md): Response: Full `KalturaUser` object with `status=1` (ACTIVE):
- [Login & Credentials](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/user-management-login-credentials.md): Grant a user the ability to log in with email + password:
- [User Roles (RBAC)](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/user-management-user-roles-rbac.md): Roles define what permissions a user has. Each role is a set of named permissions. Assign roles to users via `user[roleIds]`.
- [Groups](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/user-management-groups.md): Groups are virtual users (`type=200`) that hold membership via the `groupUser` service. Use groups as recipients in the Messaging API, notification targets in the Webhooks API, or for content entit...
- [Bulk Operations](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/user-management-bulk-operations.md): Import users from a CSV file:
- [Error Handling & Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/content-management/user-management-reference.md): Error codes, retry strategies, and best practices for User Management.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/content-moderation/moderation-overview.md): When to use moderation APIs, prerequisites, authentication, and architecture of manual and AI-powered moderation.
- [Entry Moderation Status](https://docs.kaltura.com/docs/rich-media-cms-apis/content-moderation/moderation-entry-status.md): Moderation status values, visibility rules, default behavior, and status transition diagram.
- [User Flagging](https://docs.kaltura.com/docs/rich-media-cms-apis/content-moderation/moderation-user-flagging.md): baseEntry.flag and listFlags — flag types, validation rules, permissions, and side effects.
- [Moderator Actions](https://docs.kaltura.com/docs/rich-media-cms-apis/content-moderation/moderation-actions.md): Approve, reject, list moderation queue, notifyBan, and bulk operations via multirequest.
- [AI Moderation via REACH](https://docs.kaltura.com/docs/rich-media-cms-apis/content-moderation/moderation-ai-reach.md): Order AI moderation tasks, read moderationOutputJson results, and configure category auto-actions.
- [Moderation Policies and Rules](https://docs.kaltura.com/docs/rich-media-cms-apis/content-moderation/moderation-policies.md): Text and visual moderation rules, predefined policies, custom policy creation, and scoring algorithm.
- [Category Moderation](https://docs.kaltura.com/docs/rich-media-cms-apis/content-moderation/moderation-categories.md): Per-category content gating with categoryEntry.activate and reject — comparison with entry-level moderation.
- [Player Integration](https://docs.kaltura.com/docs/rich-media-cms-apis/content-moderation/moderation-player.md): playkit-js-moderation plugin configuration, events, and viewer-facing content reporting.
- [Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/content-moderation/moderation-best-practices.md): Recommended patterns for moderation workflows, AI-first screening, and queue management.
- [Reference](https://docs.kaltura.com/docs/rich-media-cms-apis/content-moderation/moderation-reference.md): Permissions, email notifications, webhooks, REACH automation rules, error codes, and related guides.
- [Overview](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/webhooks.md): When to use webhooks, prerequisites, and a quick-start guide to your first webhook in 3 steps.
- [Core Concepts](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/webhooks-core-concepts.md): How event notifications work — template types, event types, object types, statuses, and permissions.
- [Discover System Templates](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/webhooks-discover-templates.md): List and filter available HTTP and email system templates for event notifications.
- [Clone & Configure a Template](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/webhooks-clone-configure.md): Clone HTTP or email system templates and activate them for your account.
- [HTTP Webhook Configuration](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/webhooks-http-config.md): Set webhook URLs, payloads, custom headers, authentication, user parameters, and delayed dispatch.
- [Email Notification Configuration](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/webhooks-email-config.md): Configure email recipients, templates, content parameters, and delivery for event-triggered notifications.
- [Webhook Signing](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/webhooks-signing.md): Configure HMAC signing and verify webhook payloads on your server.
- [Payload Structure](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/webhooks-payload.md): Webhook payload formats — object data, text, fields — with examples and delivery characteristics.
- [Template Management](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/webhooks-template-management.md): Get, list, update, activate, disable, and delete event notification templates.
- [Integration Patterns](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/webhooks-integration-patterns.md): Ready-to-use patterns for entry processing, caption, metadata, category, and CRM sync webhooks.
- [Error Handling & Best Practices](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/webhooks-reference.md): Error codes, retry strategies, and best practices for webhook and email notification integrations.
- [Short Links](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/short-links.md): Create and manage shortened URLs for sharing Kaltura content with expiration and status control.
- [Content Distribution](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/distribution.md): Push media to external platforms (YouTube, Facebook, FTP) via distribution profiles and automated rules.
- [Syndication Feeds](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/syndication.md): Generate RSS, MRSS, and podcast feeds that external platforms pull via HTTP GET.
- [LTI Integration](https://docs.kaltura.com/docs/rich-media-cms-apis/integration/lti.md): Integrate Kaltura video into LTI-compliant platforms (LMS, LXP) via KAF hosted middleware.

## Events & Collaboration

> **App Registry**: Kaltura App Registry API — a centralized service for registering and managing application instances (KMS sites, Events Platform instances, custom apps) used by other platform services.

> **Chat & Collaborate**: Kaltura Chat & Collaborate (CnC) — real-time chat, Q&A, polls, and reactions embedded alongside the Player in virtual events and Content Hubs pages.

> **Events Platform**: Kaltura Virtual Events Platform API — create and manage virtual town halls, webinars, conferences, and training sessions via a dedicated JSON REST API.

> **Gamification**: Kaltura Gamification (Game Services) API — leaderboards, badges, certificates, and lead scoring driven by a rules engine that processes analytics events.

> **Messaging**: Kaltura Messaging API — personalized, template-based email communications with dynamic tokens, delivery tracking, and CAN-SPAM compliant unsubscribe management.

> **User Profile**: Kaltura User Profile API — per-application user profiles, event attendance lifecycle tracking, and registration data, primarily for Events Platform integrations.

- [Overview](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-overview.md): The App Registry is a centralized service for registering and managing Kaltura application instances — KMS sites, Events Platform instances, custom applications, and more.
- [When to Use](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-when-to-use.md): Partner application management, SSO domain-based routing, developer app lifecycle, and cross-service context linking.
- [Prerequisites](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-prerequisites.md): KS permission requirements and account access needed for App Registry operations.
- [Authentication](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-authentication.md): ADMIN KS with ADMIN_BASE permission for writes; ANALYTICS_BASE also accepted for the list endpoint.
- [App Entity](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-app-entity.md): The App entity structure, app type enum, and organization domain binding fields.
- [Register an App](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-register-an-app.md): app-registry/add — required fields, response shape, uniqueness constraints, and error codes.
- [Get an App](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-get-an-app.md): app-registry/get — retrieve a full app object by GUID.
- [Update an App](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-update-an-app.md): app-registry/update — updatable fields and version-increment behavior.
- [Delete an App](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-delete-an-app.md): app-registry/delete — permanently removes an app registration.
- [Enable / Disable an App](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-enable-disable-an-app.md): app-registry/enable and app-registry/disable — toggle app status without deleting it.
- [List Apps](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-list-apps.md): app-registry/list — filter fields, pagination, and response shape.
- [Find Apps by Organization Domain](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-find-apps-by-organization-domain.md): app-registry/findByOrganizationDomain — look up app instances bound to a specific domain and app type.
- [Versioning](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-versioning.md): How the version field increments on update, enable, and disable calls.
- [Error Handling](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-error-handling.md): Application-level and validation error response shapes, error codes, and retry strategy.
- [Best Practices](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-best-practices.md): Recommended patterns including appCustomId mapping, versioning for concurrency, and common integration flows for virtual event ID to App GUID resolution.
- [Related Guides](https://docs.kaltura.com/docs/events-collaboration/app-registry-api/app-registry-related-guides.md): Links to Session, AppTokens, User Profile, Events Platform, and other related guides.
- [Overview](https://docs.kaltura.com/docs/events-collaboration/chat-and-collaborate/cnc-overview.md): The Chat & Collaborate (CnC) component provides real-time communication and audience interaction alongside video content.
- [When to Use](https://docs.kaltura.com/docs/events-collaboration/chat-and-collaborate/cnc-when-to-use.md): Virtual events and webinars, content hubs, and learning platforms that need real-time audience chat and Q&A.
- [Prerequisites](https://docs.kaltura.com/docs/events-collaboration/chat-and-collaborate/cnc-prerequisites.md): KS requirements, the CnC feature subscription, and Events Platform session setup needed before enabling CnC.
- [Features](https://docs.kaltura.com/docs/events-collaboration/chat-and-collaborate/cnc-features.md): The collaboration modules that appear alongside the player: Group Chat, Q&A, Polls, Announcements, and Reactions.
- [Integration](https://docs.kaltura.com/docs/events-collaboration/chat-and-collaborate/cnc-integration.md): How CnC is activated through the Events Platform, and the module, moderation, anonymity, and timing settings available.
- [Data Access](https://docs.kaltura.com/docs/events-collaboration/chat-and-collaborate/cnc-data-access.md): Accessing chat, Q&A, and poll engagement data through Events Platform analytics report types.
- [Error Handling](https://docs.kaltura.com/docs/events-collaboration/chat-and-collaborate/cnc-error-handling.md): Common issues with chat visibility, Q&A moderation, and poll results, and how to resolve them.
- [Best Practices](https://docs.kaltura.com/docs/events-collaboration/chat-and-collaborate/cnc-best-practices.md): Recommendations for enabling only needed modules, moderating Q&A at scale, and reviewing post-event engagement data.
- [Related Guides](https://docs.kaltura.com/docs/events-collaboration/chat-and-collaborate/cnc-related-guides.md): Links to Events Platform, Analytics Reports, Player Embed, and other related guides.
- [Overview](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-overview.md): The Virtual Events Platform has a dedicated modern REST API (OAS 3.0) for creating and managing virtual events — town halls, webinars, conferences, and training sessions.
- [When to Use](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-when-to-use.md): Event producers, enterprise communications teams, training organizations, and integration developers using the Events Platform API.
- [Prerequisites](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-prerequisites.md): KS type, plugin, and session requirements for calling the Events Platform API.
- [Authentication](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-authentication.md): Bearer KS authentication requirements — the KS must have a userId set and belong to an Events Platform team member.
- [Regional Endpoints](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-regional-endpoints.md): Events Platform base URLs for the NVP, EU, and DE regions.
- [Events API](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-events-api.md): Create, list, update, delete, and duplicate events, including duplication job status polling.
- [Sessions API](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-sessions-api.md): Session types, creating sessions within an event, listing sessions, and listing session speakers.
- [Team Members API](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-team-members-api.md): Add, list, update, and delete account-level team members (Admin, Organizer, ContentManager roles).
- [Event Templates](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-event-templates.md): Preset event templates and the session types they include.
- [Event Status Values](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-event-status-values.md): Event status values: draft, scheduled, live, ended, and cancelled.
- [Complete Example — Event Lifecycle](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-complete-example-event-lifecycle.md): End-to-end example: create an event, add a session, list events, update the event, then delete it.
- [Error Handling](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-error-handling.md): Common HTTP errors, their causes, and resolutions, plus retry strategy for transient errors.
- [Best Practices](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-best-practices.md): Recommended patterns for templates, doors-open timing, attendee management, and regional endpoints.
- [Related Guides](https://docs.kaltura.com/docs/events-collaboration/events-platform-api/events-platform-related-guides.md): Links to Session, AppTokens, Upload & Ingestion, Player Embed, and other related guides.
- [Overview](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-overview.md): The Game Services (SCM) API powers engagement mechanics for virtual events and learning platforms — leaderboards, badges, certificates, and lead scoring.
- [When to Use](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-when-to-use.md): Learning and development, event organizers, HR and compliance, marketing lead scoring, and LMS integrations.
- [Prerequisites](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-prerequisites.md): KS permission requirements and Game Services plugin activation.
- [Authentication](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-authentication.md): ADMIN KS requirements, regional endpoints, and GAME_BASE / GAME_MANAGE permissions.
- [Leaderboard Entity & CRUD](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-leaderboard-entity-crud.md): The leaderboard entity, create/get/update/list/delete operations, and sub-leaderboards for team/regional rankings.
- [Participation Policies](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-participation-policies.md): Policies controlling user visibility across game objects, and matching criteria for policy overrides.
- [Rules Engine](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-rules-engine.md): The rule entity, rule types and modes, condition operators and facts, and sub-rules for multi-stage logic.
- [Badges](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-badges.md): Badge entity with inline rules, achievement lifecycle, badge CRUD, and user badge progress.
- [Certificates](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-certificates.md): Certificate entity, PDF template configuration, credits mapping, certificate rules, and user certificate progress.
- [Lead Scoring](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-lead-scoring.md): Percentage groups and score groups, lead scoring CRUD, user lead scoring data, and lead scoring reports.
- [User Scores & Progress](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-user-scores-progress.md): Get and list user scores, per-rule progress, clearing scores, and the API v3 game plugin.
- [External Events & CSV Import](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-external-events-csv-import.md): Import scores from external systems via CSV, using delta or upsert modes.
- [Reports](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-reports.md): Report types and generating gamification data exports.
- [Scheduled Game Objects](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-scheduled-game-objects.md): Automate status transitions for game objects, such as enabling a leaderboard at event start.
- [Error Handling](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-error-handling.md): Common errors, permission errors, and standard list filters.
- [Best Practices](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-best-practices.md): Rule design, maxPoints caps, sub-rule ordering, and common integration patterns including virtual conference engagement, certification, and lead scoring.
- [Related Guides](https://docs.kaltura.com/docs/events-collaboration/gamification-api/gamification-related-guides.md): Links to Events Platform, User Profile, Analytics Reports, Messaging, Webhooks, and other related guides.
- [Overview](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-overview.md): The Messaging API enables sending personalized, template-based email communications to Kaltura users.
- [When to Use](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-when-to-use.md): Event communications, interactive audience engagement, automated lifecycle messaging, and CAN-SPAM compliant bulk messaging.
- [Authentication](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-authentication.md): ADMIN KS requirements for all Messaging API requests.
- [Email Template Entity](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-email-template-entity.md): The email template entity fields, including token maps, sender configuration, and unsubscribe groups.
- [Token Types](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-token-types.md): Token reference syntax and types: User, String, MagicLink, Dynamic, UnsubscribeUri, and JwtQrCode.
- [Manage Email Templates](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-manage-email-templates.md): Create, get, update, list, and delete email templates.
- [Send Messages](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-send-messages.md): Send to individual users or groups, and attach files to messages.
- [Message Lifecycle](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-message-lifecycle.md): Bulk and discrete message status values, engagement tracking events, and discrete error codes.
- [Track Messages](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-track-messages.md): List bulk messages, group by session, get message statistics, and view discrete message details.
- [Delivery Reports](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-delivery-reports.md): Generate CSV delivery reports for a bulk message or session.
- [Unsubscribe Management](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-unsubscribe-management.md): Unsubscribe groups, user unsubscribe status and preferences, and unsubscribe URI configuration.
- [Email Provider Configuration](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-email-provider-configuration.md): Configure a custom SendGrid provider, provider lookup resolution order, and assigning providers to apps.
- [Domain Configuration](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-domain-configuration.md): Add and activate sender domains for improved deliverability.
- [Error Handling](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-error-handling.md): Bulk message error codes and retry strategy.
- [Best Practices](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-best-practices.md): CAN-SPAM compliance, dynamic tokens, domain authentication, and common integration patterns including event invitation workflows.
- [Related Guides](https://docs.kaltura.com/docs/events-collaboration/messaging-api/messaging-related-guides.md): Links to Session, AppTokens, App Registry, User Profile, Events Platform, and other related guides.
- [Overview](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-overview.md): The User Profile service manages per-application user profiles, primarily for the Events Platform attendance lifecycle.
- [When to Use](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-when-to-use.md): User preference management, profile customization, viewer personalization, and event registration workflows.
- [Authentication](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-authentication.md): ADMIN KS with ADMIN_BASE permission for writes; ANALYTICS_BASE or EP_USER_ANALYTICS accepted for the eventDataStats report.
- [Prerequisites](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-prerequisites.md): The user must already exist as a KalturaUser, and the app must be registered and enabled in the App Registry.
- [User Profile Entity](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-user-profile-entity.md): The profile entity fields, login data, event data, and registration origin values.
- [Attendance Status Lifecycle](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-attendance-status-lifecycle.md): The attendanceStatus lifecycle, status values, and automatic side effects on status transitions.
- [Create a User Profile](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-create-a-user-profile.md): user-profile/add — required fields, response shape, and error codes.
- [Bulk Create User Profiles](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-bulk-create-user-profiles.md): user-profile/bulkAdd — create multiple profiles for the same app in one request.
- [Get a User Profile](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-get-a-user-profile.md): user-profile/get by ID, and user-profile/getByFilter for lookup by app and user.
- [Update a User Profile](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-update-a-user-profile.md): user-profile/update — merge behavior for eventData/loginData vs. full replacement for profileData/appData.
- [List User Profiles](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-list-user-profiles.md): user-profile/list — filter fields, pagination, sorting, and total count.
- [Delete a User Profile](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-delete-a-user-profile.md): user-profile/delete — soft-delete behavior and re-registration after deletion.
- [Reports](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-reports.md): Event data statistics, first-attendance-per-app counts, and CSV/engagement reports.
- [Error Handling](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-error-handling.md): Error response shapes, error codes, and retry strategy.
- [Best Practices](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-best-practices.md): Bulk registration, App Registry resolution, attendance lifecycle tracking, and common integration patterns including PII deletion.
- [Related Guides](https://docs.kaltura.com/docs/events-collaboration/user-profile-api/user-profile-related-guides.md): Links to App Registry, Session, AppTokens, Events Platform, Messaging, and other related guides.

## Embeddable Kaltura products

> **Kaltura Player**: Embed the PlayKit player via iframe or JavaScript — autoplay, clipping, access control, and programmatic player API.

> **Media Manager**: Embeddable media library UI for browsing, searching, and selecting Kaltura content entries.

- [Overview](https://docs.kaltura.com/docs/embeddable-kaltura-products/kaltura-player/player-embed-overview.md): When to use player embedding, prerequisites, authentication, and embed type comparison.
- [Iframe Embed](https://docs.kaltura.com/docs/embeddable-kaltura-products/kaltura-player/player-embed-iframe.md): Embed Kaltura Player via iframe with query string parameters for playback, clipping, and autoplay.
- [Dynamic JS (PlayKit) Embed](https://docs.kaltura.com/docs/embeddable-kaltura-products/kaltura-player/player-embed-dynamic-js.md): Load PlayKit via JavaScript, configure KalturaPlayer.setup() and loadMedia() for programmatic embedding.
- [JS Control & Events](https://docs.kaltura.com/docs/embeddable-kaltura-products/kaltura-player/player-embed-js-control.md): Play/pause/seek APIs, HTML5 and custom player events, 30+ plugin ecosystem, and runtime plugin control.
- [Server-Side KS](https://docs.kaltura.com/docs/embeddable-kaltura-products/kaltura-player/player-embed-server-ks.md): Generate scoped USER KS for player embeds with entry, privacy, and IP tokenization privileges.
- [Progress Tracking](https://docs.kaltura.com/docs/embeddable-kaltura-products/kaltura-player/player-embed-progress-tracking.md): Track playback quartile milestones (25%, 50%, 75%, 100%) using TIME_UPDATE events.
- [Reference](https://docs.kaltura.com/docs/embeddable-kaltura-products/kaltura-player/player-embed-reference.md): Error handling, retry strategies, best practices, and related guides for player embedding.
- [Video Quiz](https://docs.kaltura.com/docs/embeddable-kaltura-products/kaltura-player/video-quiz.md): Create interactive video quizzes with cue-point questions, scoring models, and attempt tracking.
- [Chapters & Slides](https://docs.kaltura.com/docs/embeddable-kaltura-products/kaltura-player/chapters-slides.md): Add navigable chapter markers and synced presentation slides to videos using thumb cue points.
- [Annotations](https://docs.kaltura.com/docs/embeddable-kaltura-products/kaltura-player/annotations.md): Create timestamped text annotations with threaded replies and interactive hotspot overlays on video.
- [Cue Points & Interactive Videos](https://docs.kaltura.com/docs/embeddable-kaltura-products/kaltura-player/cue-points.md): Hub guide for the cue point system: architecture, base service, and cross-type features for interactive video.
- [Ads Cue Points](https://docs.kaltura.com/docs/embeddable-kaltura-products/kaltura-player/ads-cue-points.md): Insert pre-roll, mid-roll, post-roll, and overlay ads using VAST/VPAID ad cue points.
- [Code, Events & Session Cue Points](https://docs.kaltura.com/docs/embeddable-kaltura-products/kaltura-player/code-cue-points.md): Use code cue points for custom player triggers, dual-screen layout switches, and broadcast event markers.
- [Getting Started](https://docs.kaltura.com/docs/embeddable-kaltura-products/media-manager/getting-started.md): Quick-start guide to embed the Media Manager component using a KS token and partner ID.
- [Uploads](https://docs.kaltura.com/docs/embeddable-kaltura-products/media-manager/uploads.md): Enable and configure the upload button, allowed file types, and background upload status display.
- [Row Actions](https://docs.kaltura.com/docs/embeddable-kaltura-products/media-manager/row-actions.md): Configure inline buttons and dropdown menu actions on each media table row, including selection callbacks.
- [Header](https://docs.kaltura.com/docs/embeddable-kaltura-products/media-manager/header.md): Configure the header area with search filters, media-type chips, upload button, and breadcrumbs.
- [Data & Credentials](https://docs.kaltura.com/docs/embeddable-kaltura-products/media-manager/data.md): Filter media by type, set page size, browse by category, and configure KS credentials for the component.
- [Examples](https://docs.kaltura.com/docs/embeddable-kaltura-products/media-manager/examples.md): Ready-to-use mountVisual examples: media picker dialog, full-featured inline table, and more.