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 Sessions API

Manage and query meeting sessions and participants.

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

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

This API exposes 6 operations across 6 paths, and defines 5 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.

6 operations 6 paths 5 schemas 6 GET

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 Sessions 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 6

Across 6 paths, the API surfaces 6 operations — 6 GET. Each is listed below with its method, path, parameters, and response codes.

Sessions 6

Manage and query meeting sessions and participants.

GET
/sessions
Fetch Sessions
fetchSessions 4 params → 200401
GET
/sessions/{sessionId}
Fetch a Session
fetchSession 1 param → 200404
GET
/sessions/{sessionId}/participants
Fetch Participants
fetchParticipants 1 param → 200404
GET
/sessions/{sessionId}/participants/active
Fetch Active Participants
fetchActiveParticipants 1 param → 200
GET
/sessions/{sessionId}/stats
Fetch Session Quality Stats
fetchSessionStats 1 param → 200
GET
/sessions/{sessionId}/participant/{participantId}/stats
Fetch Peer Quality Stats
fetchParticipantStats 2 params → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Session (7 properties), PageInfo (4 properties), Participant (3 properties), SessionsResponse (2 properties). Each schema is shown below with its type and property counts.

PageInfo
object
4 properties
Participant
object
3 properties
Error
object
2 properties
SessionsResponse
object
2 properties
Session
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

videosdk-sessions-api-openapi.yml Raw ↑

Other APIs VideoSDK publishes across the network.

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

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