VdoCipher

VdoCipher is DRM-protected video hosting with encrypted streaming, dynamic watermarking, and per-viewer playback authorization. Agents import and upload videos, generate playback OTPs, organize folders and tags, add posters and captions, track bandwidth, and react to VdoCipher events.

Verified 1 trigger 27 actions API key available

VdoCipher website Platform Documentation Capability data verified 2026-08-28

A learner opens a lesson page in the course platform

Agent resolves the learner's identity and the entitlement that backs this lesson

Get Video confirms the status reads ready, since only a ready video can produce a usable playback token

Agent assembles this session's restriction set: the viewer's own watermark text, the allowed window, the geography

Generate Playback OTP issues the token and playbackInfo pair the player needs

Agent logs the issued session against the learner's record for the access audit

The content owner rules on any request to drop the watermark or widen the window

What This Integration Enables

VdoCipher exists for content whose value depends on not being copied: paid courses, licensed footage, exam material, subscriber-only libraries. Its API makes that concrete in a way most video hosts do not. An encrypted video simply cannot be played without a one time password and a playbackInfo pair issued server side, and every restriction the platform offers, the dynamic watermark, the allowed window, the geographic and network limits, is applied when that token is issued rather than stored on the video.

That single design choice reorganizes the whole integration. The video record is nearly inert. The interesting object is the session, and the session is created by an operation your agent calls. FlowRunner agents import and upload videos, delegate uploads to a content provider's browser without the bytes ever touching your servers, organize a library into folders and tags, attach posters and caption tracks, read per-video bandwidth the dashboard does not show, and issue the playback tokens that decide who watches what. The vendor is explicit that the key which issues those tokens can issue them for the entire library, which is precisely why a human-in-the-loop gate belongs on the exceptions rather than on the routine.

Without FlowRunner

Protection assumed from a private URL The file is unlisted rather than encrypted, and an unlisted URL travels

Leaks with no trail A recording surfaces and there is no way to tell whose session it came from

Upload pipelines that move every byte twice Media is pulled into the flow and pushed out again even when a URL would do

With FlowRunner

Protection enforced at playback The video cannot play at all without a token issued server side for that session

Leaks that carry an identity The watermark is set per session, so a recording points back at a viewer

Upload pipelines that move bytes once A reachable source is handed over as a URL, and delegated uploads bypass the flow entirely

Use Case Scenarios

Playback provisioned by entitlement, per session

A learner opens a lesson in Teachable or a members area built on Memberstack. The agent checks the enrollment, confirms the video's status is ready with Get Video, and calls Generate Playback OTP with the restriction set for that person: their email rendered into the dynamic watermark, an expiry that matches the session, and the geography their enrollment allows. The player receives the token pair and nothing else. When a subscription lapses in Stripe, no further tokens are issued, which is what actually ends access.

A supplier's footage that never touches your servers

A production partner has a large file and no appetite for a transfer dance. The agent calls Create Upload Credentials, which reserves a video id and returns short lived credentials, and hands those to the partner's browser so the upload goes straight into your VdoCipher account. When the source is a public URL instead, the agent prefers Import Video From URL, which hands VdoCipher the address and moves no bytes at all, and sets the title in the same call rather than renaming afterward and producing a second callback. The On VdoCipher Event trigger reports when encoding finishes, and the agent files the video with Move To Folder and Add Tags.

A cost report the dashboard cannot produce

Finance wants to know which titles are consuming the bandwidth. The dashboard reports only daily account totals, so the agent calls Get Video Bandwidth Usage for the previous UTC day, after the vendor's stated accounting window has closed, and parses the returned rows of video id and kilobytes. It joins those against titles from List Videos, appends the day to a running sheet in Google Sheets, and posts the top consumers to the operations channel in Slack when a title breaks its usual pattern.

Human-in-Loop Highlight

Generate Playback OTP is the only enforcement point on this platform, and it enforces nothing it was not told. The dynamic watermark, the expiry, the IP and geographic limits are all properties of the token, not of the video, so a token issued without them is an unrestricted, unattributable playback session for content that is otherwise unplayable. There is no operation here that revokes an OTP once it has been issued, and deleting the video does not help either, because the vendor warns that CDN caching can let a deleted video keep playing for a while afterward. Which means the routine case should run unattended and the exception should not. When a request arrives to relax the restrictions, the agent stops: "Request from the enterprise account to issue tokens for the 42 videos in the Certification track with the viewer watermark disabled, because their learners say it is distracting. Disabling it removes the only thing that ties a leaked recording to a specific viewer, and sessions already issued cannot be recalled. Approve, deny, or approve with a shorter expiry instead?" The content owner decides. The agent then issues exactly the token set that was approved and logs every one against the learner it was issued for. Provisioning thousands of ordinary sessions is machine work. Deciding to hand out an untraceable one is not.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

27 actions

Playback

Generate Playback OTP Issues the one time password and playbackInfo pair a VdoCipher player needs, which is the whole point of the API, since an encrypted video cannot play without one. It must be generated server side because it requires the secret key, and every restriction is applied here at token time rather than on the video. The operation this page's human gate exists for.

Videos

List Videos Lists videos newest first, with filters for tag and folder and a free text search across id and title.
Get Video Reads a video's status and details. The status is the field that matters and is not the HTTP status: only a ready video can produce a usable playback token.
Get Video Metadata Reads a video's metadata including long lived, CDN backed poster image URLs that can be stored and used directly as thumbnails. This and the token endpoint are the two the vendor considers safe to call at web scale.
Import Video From URL Imports a video from an HTTP or FTP URL, which is the cheapest way to get media in: no bytes pass through the flow and no upload credentials are needed. Setting the title here saves a second call and a second callback.
Create Upload Credentials Reserves a video id and returns short lived credentials for uploading directly to VdoCipher storage. Its real purpose is delegation, since the credentials can be handed to a content provider's browser so their video never passes through your servers.
Upload Video From URL Uploads a video by reading it from a URL the flow can reach and posting it with the credentials VdoCipher issues. Use it only when importing cannot, since importing moves no bytes at all.
Rename Video Changes a video's title. The vendor recommends setting the title at upload or import time instead, because renaming produces a second callback for the same video.
Delete Videos Deletes one or more videos and stops them counting toward the storage allowance. Deletion is not instantaneous from a viewer's point of view, since CDN caching can let a deleted video keep playing briefly, so this is not the way to cut off access.

Folders

List Folder Lists the subfolders inside one folder. The top level folder's id is the literal string root.
List All Folders Lists every folder and subfolder on the account in one response, which is how the whole tree is mapped without walking it.
Create Folder Creates a folder under a parent. VdoCipher allows two folders with the same name under the same parent, so a flow creating folders dynamically should search first.
Rename Folder Renames a folder. Its contents and its place in the tree are unchanged.
Delete Folder Deletes a folder. No video is lost, since videos inside move up to the parent, so this removes the grouping only.
Move To Folder Moves videos and folders into another folder in one call, which is how a library is reorganized without touching each item.
Search Folders Finds folders by name and returns each match's id and path. It exists because folder names are not unique, so it is the check to run before creating one.

Files

List Video Files Lists every file attached to a video: the original upload, the encoded renditions, the generated and uploaded posters, and the caption tracks. Its ids are what the delete and download operations take.
Delete Video File Deletes one file from a video, which is how a caption or poster is removed before a replacement is uploaded. The vendor labels it potentially destructive and says files are removed almost immediately, so the id should come from a listing rather than a guess.
Upload Poster Image Replaces a video's poster image with one fetched from a URL. VdoCipher generates posters automatically from a random frame, so this is how a deliberate thumbnail is set. It adds a poster rather than removing the old ones.
Upload Captions Adds a WebVTT caption track in a given language, identified by an ISO 639-1 code. A second track for a language that already has one is added alongside rather than replacing it.

Account

Get Video Bandwidth Usage Returns per video bandwidth consumption for one UTC day, which the dashboard does not show at all since it reports only daily account totals. The day's accounting runs the following morning, and the response is CSV of video id and kilobytes returned here as raw text plus parsed rows.

Webhooks

List Webhooks Lists the account's webhook subscriptions, including any the trigger created, which is how orphaned hooks from a deleted flow are found.
Create Webhook Subscribes a URL to a video status event. A subscription names one event, so watching both means two subscriptions. Use this to point VdoCipher at something outside FlowRunner.
Delete Webhook Removes a webhook subscription. VdoCipher takes the id in the request body of a DELETE rather than in the path, which is where hand written clients usually go wrong.

Triggers

1 triggers

Event Triggers

On VdoCipher Event Fires when a video finishes encoding and becomes playable. VdoCipher publishes two events: one per video as it becomes ready, and one that fires once when a whole batch is done.

Frequently Asked Questions

What can FlowRunner do with VdoCipher?

FlowRunner agents can run Generate Playback OTP, List Videos, and Get Video in VdoCipher, plus 24 more actions.

Does connecting VdoCipher to FlowRunner require OAuth?

No. VdoCipher connects to FlowRunner with an API key, no OAuth flow required.

Can VdoCipher trigger a FlowRunner workflow automatically?

Yes. VdoCipher supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with VdoCipher

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us