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.

Can I limit what my agent is allowed to do with the Panopto API?

Yes. Because you run Jentic One yourself, your own rules decide which Panopto operations and credentials the agent may use. Panopto puts the recorder and session ids in the URL path, such as /remoteRecorder/{remoteRecorderPublicId} and /session/{sessionId}, so you can pin the agent to a single recorder or session and to only the operations you approve, like pausing and resuming a recording or reading a schedule. Operations you do not approve, such as disconnecting a recorder, stay off limits unless you explicitly add them.