Draft: these docs describe OctaVideo as it will be at launch; some features may not be live yet.
OctaVideoDocs

API reference

The OctaVideo server API, endpoint by endpoint, generated from its OpenAPI spec.

The server API lets your backend upload and manage videos and issue playback OTPs. Each endpoint has its own page with parameters, request and response schemas, and code samples.

Basics

Base URLhttps://api.octavideo.tech/api/v1
AuthenticationThe library's private key in the AccessKey header. See Authentication.
FormatJSON in and out, except uploads (multipart/form-data).
SuccessThe payload in data; lists add meta. See Pagination.
Errors{ "error": { "code", "message", "request_id" } }. See Errors.
SpecOpenAPI 3.1, JSON

Endpoints

MethodPathWhat it does
POST/videos/uploadUpload a video file
POST/videos/importImport from Google Drive, OneDrive or a URL
GET/videosList videos
GET/videos/{videoId}Get a video and its processing status
PUT/videos/{videoId}/detailsUpdate the title and description
PUT/videos/{videoId}/chaptersReplace the chapters
POST/videos/{videoId}/transcribeStart a transcription
GET/videos/{videoId}/thumbnailsList thumbnail URLs
POST/collectionsCreate a collection
POST/collections/{collectionId}/videosAdd videos to a collection
POST/playback/otpIssue a playback OTP and embed URL

No in-browser playground

The server API is called from your server with your library's private key, which must never reach a browser. Try requests with cURL, or with one of the SDKs.

Use the spec in your tools

Download openapi.json to generate a typed client, import the API into Postman or Insomnia, or give an AI coding assistant the exact contract. /llms.txt lists every page of these docs as Markdown for AI agents.

On this page