Panopto Public API

★ Only Publicly Available OpenAPI DocumentMediaVideohttp8 EndpointsREST

For Agents

Manage remote recorders, control recording sessions, monitor live streams, and handle authentication across 8 endpoints.

Install Jentic One Beta

Connect the Panopto Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Panopto Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Panopto Public API.

Authenticate using legacy login method

Connect and disconnect remote recorders

Send heartbeat signals to maintain recorder connections

GET STARTED

Start building with Panopto Public API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Panopto Public API for, with concrete tasks.

★ Remote Recorder Management

Register and manage remote recording devices in the Panopto platform. POST /api/v1/remoteRecorderAPI/remoteRecorder registers a new recorder, followed by POST /api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/connect to establish connection. Maintain connection with periodic POST heartbeat calls.

POST /api/v1/remoteRecorderAPI/remoteRecorder to register, then POST /connect to establish connection, followed by periodic heartbeat calls

Recording Session Control

Control active recording sessions with pause and resume operations. POST /api/v1/remoteRecorderAPI/session/{sessionId}/pause pauses recording, and POST /resume restarts it. Essential for lecture capture workflows where instructors need session control without stopping the entire recording.

POST /api/v1/remoteRecorderAPI/session/{sessionId}/pause to pause, and POST /resume to continue recording

Schedule-Driven Recording

Retrieve and manage recording schedules for remote recorders. GET /api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/schedule returns scheduled recording times and configurations, enabling automated lecture capture based on class schedules.

GET /api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/schedule to retrieve recording schedule

Agent-Driven Video Platform Management via Jentic

An AI agent managing educational technology infrastructure can register recorders, control recording sessions, and monitor schedules through Jentic without exposing bearer authentication tokens in agent context. Jentic resolves intents like 'pause the recording' to the right Panopto endpoint.

Search Jentic for 'pause a recording session', load the POST /session/{sessionId}/pause schema, and execute

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for panopto public api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v1/auth/legacyLogin

Legacy login authentication

POST

/api/v1/remoteRecorderAPI/remoteRecorder

POST

/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/connect

Connect remote recorder

POST

/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/disconnect

Disconnect remote recorder

POST

/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/heartbeat

Remote recorder heartbeat

GET

/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/schedule

Get recorder schedule

POST

/api/v1/remoteRecorderAPI/session/{sessionId}/pause

Pause recording session

POST

/api/v1/remoteRecorderAPI/session/{sessionId}/resume

Resume recording session

POST

/api/v1/auth/legacyLogin

Legacy login authentication

POST

/api/v1/remoteRecorderAPI/remoteRecorder

POST

/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/connect

Connect remote recorder

POST

/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/disconnect

Disconnect remote recorder

POST

/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/heartbeat

Remote recorder heartbeat

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Panopto's bearer token is stored encrypted in the Jentic vault and injected at execution time. Agents receive scoped access — the raw token never enters agent context.

Intent-based discovery

Agents search by intent (e.g. 'pause a recording', 'register a remote recorder') and Jentic returns the matching Panopto endpoint with the request schema pre-shaped for execution.

Time to first call

Direct Panopto integration: 2-5 days including authentication setup, endpoint discovery, and testing. Through Jentic: under 1 hour once credentials are configured — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Zoom API

Video conferencing platform with recording capabilities and meeting management

Choose Zoom API when the workflow requires video conferencing features alongside recording, rather than dedicated lecture capture

Alternative

Kaltura API

Video platform for media management, transcoding, and delivery with extensive video operations

Choose Kaltura API when the workflow needs comprehensive video content management beyond lecture capture

FAQs

Specific to using Panopto Public API through Jentic.

Why is there no official OpenAPI spec for Panopto Public API?

Panopto does not publish a complete OpenAPI specification for their public API endpoints. Jentic generates and maintains this spec so that AI agents and developers can call Panopto Public API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Panopto Public API use?

The Panopto Public API uses bearer token authentication. Through Jentic, the token is stored in the encrypted vault and injected at execution time so it never enters the agent's prompt context.

Can I control recording sessions with the Panopto Public API?

Yes. POST /api/v1/remoteRecorderAPI/session/{sessionId}/pause pauses an active recording, and POST /resume restarts it. These endpoints enable real-time control of lecture capture and video recording sessions.

How do I register a remote recorder with Panopto?

POST /api/v1/remoteRecorderAPI/remoteRecorder registers a new remote recorder. After registration, use POST /connect with the remoteRecorderPublicId to establish connection, and maintain it with periodic heartbeat calls.

What is the purpose of the heartbeat endpoint?

POST /api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/heartbeat keeps the remote recorder connection active. Send periodic heartbeat requests to prevent connection timeout and ensure the recorder remains available for scheduled recordings.

Can I retrieve recording schedules via the API?

Yes. GET /api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/schedule returns the recording schedule for a specific remote recorder, including scheduled times and configurations for automated lecture capture.