OctaVideo documentation
Host, protect and securely play your videos, from the console or from your own server.
OctaVideo hosts the videos you sell or teach with, encrypts them, and plays them only for the viewers you allow. These docs cover the console your team uses every day and the API your developers call from your own server.
Quickstart
Create a library, upload a video and put it on your site in about 5 minutes.
Core concepts
Libraries, regions, videos, private keys and one-time playback passwords.
Secure playback
Issue an OTP from your server for every viewer and every page view.
API reference
Every endpoint of the server API, with request and response examples.
Who these docs are for
- Publishers upload videos, add chapters and transcripts, and choose how the player looks. Start with the console guides.
- Developers connect your website or LMS to OctaVideo: they request a one-time password (OTP) for each viewer and embed the player. Start with authentication.
- Account owners manage the plan, the balance and the invoices. See how billing works.
How OctaVideo works
Create a library. A library holds your videos, their encoding and player settings, and their security rules. Its storage region is fixed when you create it.
Upload or import videos. OctaVideo encodes each video into several resolutions and encrypts it. The video is Ready when processing finishes.
Embed the player. Paste a ready-made iframe, or have your server request an OTP for each viewer. The player only plays on the domains you allow.
Private beta
OctaVideo is in private beta. Workspaces open by invitation, and the API may still change before general availability. Questions? Write to help@octavideo.tech.