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

VideoSDK Participant Recordings API

Per-participant recording management.

VideoSDK Participant Recordings API is one of 7 APIs that VideoSDK publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 5 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.0.3, at version 2.0.

Requests are made against a single base URL, https://api.videosdk.live/v2.

5 operations 4 paths 4 schemas 1 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2.0
Base URL
https://api.videosdk.live
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

VideoSDK Participant Recordings API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (JWTAuth). By default, every request must be authenticated.

  • JWTAuth — JWT token generated using your VideoSDK API key and secret (HS256). Pass the token directly without a "Bearer" prefix.

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Participant Recordings 5

Per-participant recording management.

POST
/recordings/participant/start
Start Participant Recording
startParticipantRecording body → 200
POST
/recordings/participant/stop
Stop Participant Recording
stopParticipantRecording body → 200
GET
/recordings/participant
Fetch All Participant Recordings
fetchParticipantRecordings 3 params → 200
GET
/recordings/participant/{participantRecordingId}
Fetch Single Participant Recording
fetchParticipantRecording 1 param → 200
DELETE
/recordings/participant/{participantRecordingId}
Delete Participant Recording
deleteParticipantRecording 1 param → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Recording (8 properties), RecordingConfig (5 properties), PageInfo (4 properties), LayoutConfig (3 properties). Each schema is shown below with its type and property counts.

RecordingConfig
object
5 properties
PageInfo
object
4 properties
LayoutConfig
object
3 properties
Recording
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

videosdk-participant-recordings-api-openapi.yml Raw ↑

Other APIs VideoSDK publishes across the network.

VideoSDK HLS Streaming API
VideoSDK Recordings API
VideoSDK Rooms API
VideoSDK RTMP Streaming API
VideoSDK Sessions API
VideoSDK Track Recordings API
Where this information came from

This is an independent, third-party profile of VideoSDK Participant Recordings 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.