Core concepts
Workspaces, assets, uploads, processing and playback sessions.
Workspace
Section titled “Workspace”Your workspace (a tenant in the API) contains everything your organisation creates: assets, uploads, API keys and playback sessions. Workspaces are fully isolated from each other.
People in a workspace have a role:
| Role | Can |
|---|---|
owner | Everything, including managing API keys and team members |
admin | Everything, including managing API keys |
member | Work with assets, uploads and playback |
Assets
Section titled “Assets”An asset is one lesson: its metadata, its source file and every version WireVoD prepares for playback.
| Status | Meaning |
|---|---|
pending | Created and waiting for its source file |
uploaded | The source file is safely stored; processing is queued |
processing | WireVoD is preparing the lesson for playback |
ready | Published and ready to stream |
failed | Processing couldn’t complete; failure_code explains why. A failed asset accepts a new upload |
Once processed, an asset describes its source (source_width, source_height,
source_duration_ms and more). Whether an asset is protected (drm_enabled) is decided when
it’s created and never changes.
Uploads
Section titled “Uploads”An upload moves a source file into WireVoD. Files go directly from your client to secure storage in parts, so large lessons upload quickly and survive dropped connections. See Uploading videos.
Processing
Section titled “Processing”When an upload completes, WireVoD’s Adaptive Intelligence analyses the lesson and prepares a set
of versions tailored to its content, so learners on any screen and connection get a sharp, smooth
picture while you store and stream as little as possible. Protected assets are sealed for
content protection in the same pass. Every result is checked before the asset
becomes ready.
You don’t configure any of this. Upload the best source you have; WireVoD handles the rest.
Playback sessions
Section titled “Playback sessions”A playback session gives one viewer time-limited access to one asset. Your backend creates it after your own checks (enrolment, payment, cohort); the learner’s browser receives only the session’s URLs. Sessions last from one minute to 24 hours and can be revoked at any time. See Playback & access.