How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Panopto RemoteRecorderAPI API

Remote Recorder Device API. Warning: this endpoint is for Panopto's hardware partners only and cannot be used without a partner API key.

Panopto RemoteRecorderAPI API is one of 16 APIs that Panopto publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include RemoteRecorderAPI. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 16 operations across 15 paths, and defines 38 schemas. It is described by OpenAPI 2.0, at version 1.

Requests are made against the base URL https://{tenant}.hosted.panopto.com/Panopto/api/v1.

16 operations 15 paths 38 schemas 3 GET12 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
1
Base URL
https://{tenant}.hosted.panopto.com/Panopto/api/v1
Resource Areas
1

Paths & Operations 16

Across 15 paths, the API surfaces 16 operations — 3 GET, 12 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

RemoteRecorderAPI 16

Remote Recorder Device API. Warning: this endpoint is for Panopto's hardware partners only and cannot be used without a partner API key.

PUT
/api/v1/remoteRecorderAPI/remoteRecorder
Register a new remote recorder
RemoteRecorderAPI_RegisterRemoteRecorder 1 param → 200400
POST
/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/connect
Connect as the provided remote recorder
RemoteRecorderAPI_Connect 3 params → 400
POST
/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/disconnect
Disconnect as the provided remote recorder, identified via the GUID public id
RemoteRecorderAPI_Disconnect 1 param → 400
POST
/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/heartbeat
Heartbeat and preview as the provided remote recorder
RemoteRecorderAPI_Heartbeat 3 params → 200400
GET
/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/schedule
Retrieve a schedule for the next 7 days for the provided remote recorder.As a best practice a new scheduled should be fetched every day even if the schedule version in the heartbeat hasn't changed
RemoteRecorderAPI_GetSchedule 2 params → 200400
POST
/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/schedule
Update or add a set of scheduled recordings for the provided remote recorder. To add a scheduled recording, the recording should have all relevant fields filled in but an empty (all zeros) guid
RemoteRecorderAPI_UpdateSchedule 2 params → 400
POST
/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/error
Register an error with the provided remote recorder on the server
RemoteRecorderAPI_Error 2 params → 400
GET
/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/legacyLogin
Retrieve a legacy ASPXAUTH cookie
RemoteRecorderAPI_LegacyLogin 1 param → 401
POST
/api/v1/remoteRecorderAPI/session/{sessionId}/pause
Pause the recording of the specified session on the server
RemoteRecorderAPI_PauseRecording 2 params → 400
POST
/api/v1/remoteRecorderAPI/session/{sessionId}/resume
Resume the recording of the specified session on the server
RemoteRecorderAPI_ResumeRecording 2 params → 400
POST
/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/urls
Provides a list of URLs and URL types to present to administrators to help them manage this remote recorder.Calling this replaces all previously reported URLs. URLs are preserved until replaced, so t…
RemoteRecorderAPI_ReportRemoteRecorderURLs 2 params → 400
POST
/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/liveMonitoring/webRtc/connect
Establishes a new connection which enables the WebRTC-based media preview feature. After this, the client should commence WebRTC session negotiation by sending us an SDP offer.
RemoteRecorderAPI_WebRtcConnect 2 params → 200400401503
POST
/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/liveMonitoring/webRtc/disconnect
Destroys the connection which enables the WebRTC-based media preview feature.
RemoteRecorderAPI_WebRtcDisconnect 2 params → 200400401
GET
/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/liveMonitoring/webRtc/events
After the client has sent us an SDP offer, they should poll this endpoint periodically to receive messages.
RemoteRecorderAPI_WebRtcGetEvents 1 param → 200400401
POST
/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/liveMonitoring/webRtc/iceCandidates
Sends a batch of ICE candidates from client to signaling server.
RemoteRecorderAPI_WebRtcIceCandidates 2 params → 200400401
POST
/api/v1/remoteRecorderAPI/remoteRecorder/{remoteRecorderPublicId}/liveMonitoring/webRtc/sdpOffer
The client begins WebRTC session negotiation by submitting an SDP offer.
RemoteRecorderAPI_WebRtcSdpOffer 2 params → 200400401

Schemas 38

The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are RemoteRecorderScheduledRecording (14 properties), RemoteRecorderConfiguration (8 properties), RemoteRecorderError (5 properties), RemoteRecorderRegistrationRequest (5 properties). Each schema is shown below with its type and property counts.

LiveMonitoringHeartbeatResponseData
object
2 properties 1 required
WebRtcEventType
string
LiveMonitoringMode
string
WebRtcIceCandidates
object
1 property
RemoteRecorderDevicePreview
object
5 properties 2 required
Device
object
3 properties 1 required
RemoteRecorderAudioHistogramType
string
RemoteRecorderPauseRecordingRequest
object
1 property 1 required
RemoteRecorderErrorType
string
WebRtcDisconnectPostData
object
1 property 1 required
RemoteRecorderSchedule
WebRtcSdpOfferPostData
object
1 property
RemoteRecorderState
string
RemoteRecorderURL
object
2 properties 1 required
RemoteRecorderHeartbeatData
object
5 properties 3 required
WebRtcIceCandidate
object
2 properties 1 required
RemoteRecorderHeartbeatResponse
DeviceType
string
RemoteRecorderRegistrationResponse
RemoteRecorderURLType
string
WebRtcEventsResponse
RemoteRecorderError
object
5 properties 3 required
RemoteRecorderRegistrationRequest
object
5 properties
DeviceDescriptionWithPreview
object
2 properties
RemoteRecorderErrorSeverity
string
RemoteRecorderScheduledRecording
object
14 properties 7 required
RemoteRecorderResumeRecordingRequest
object
1 property 1 required
QualitySettings
object
5 properties 5 required
WebRtcDisconnectOperationType
string
WebRtcConnectPostData
object
1 property 1 required
WebRtcConnectOperationType
string
APIErrorInternal
object
4 properties 1 required
RemoteRecorderURLsUpdateRequest
object
1 property
RemoteRecorderConfiguration
object
8 properties 4 required
APIError
object
1 property
WebRtcEvent
object
2 properties 1 required
DeviceThumbnailFormat
string
RemoteRecorderExtendedConfiguration
object
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

panopto-remoterecorderapi-api-openapi.yml Raw ↑

Other APIs Panopto publishes across the network.

Panopto Accessibility API
Panopto Auth API
Panopto CaptionProviders API
Panopto Folders API
Panopto Groups API
Panopto Playlists API
Panopto RemoteRecorders API
Panopto Reports API
Panopto ScheduledRecordings API
Panopto SearchIndexSyncUpdates API
Panopto Sessions API
Panopto Streams API
Where this information came from

This is an independent, third-party profile of Panopto RemoteRecorderAPI API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.