Simple upload API
Send a source file, poll or receive a webhook, and store the returned playback URL.
curl -X POST https://api.voomy.net/uploads \
-H "authorization: Bearer $VOOMY_API_KEY" \
--data-binary @launch-video.mp4
{
"jobId": "job_8f7c...",
"status": "processing"
}
100,000 playback minutes can stay inexpensive before library size, processing, and support.
Video backend API for cost-sensitive apps
Voomy converts source videos into streamable playback URLs with predictable costs, simple controls, and no full video-platform overhead.
Not a full video platform. Not another infrastructure project. Voomy is the thin layer between upload and inexpensive adaptive playback.
Why it exists
If you need DRM, live streaming, deep analytics, or a branded player, use a larger platform. If you mostly need upload, playback, and predictable delivery economics, use less.
Send a source file, poll or receive a webhook, and store the returned playback URL.
Each processed video gets a playback URL your app can store, share, or embed.
Plans cap uploads, processing minutes, video library size, playback volume, and concurrent jobs.
Workflow
Post an MP4 or MOV from your server, CLI, or direct-upload flow.
Create playback options that stay smooth across connection speeds.
Return a playback URL your product can use immediately.
Pricing shape
Early plans are designed for teams that would rather cap usage than negotiate video platform contracts.
$9/mo
Most likely
$29/mo
Talk/mo
API docs
Voomy includes the full OpenAPI reference for uploads, processing jobs, metadata, manifests, segment ranges, source downloads, and deletion.
Authenticated endpoints accept either an Authorization bearer token or an
x-api-key header. Public playback metadata and manifest routes stay open.
Authorization: Bearer $VOOMY_API_KEY
x-api-key: vmy_live_...
Upload MP4, MOV, AVI, Matroska, or octet-stream source files. Optional
title, expires_in, expires_at, and
x-video-title values can travel with the request.
Poll queued, processing, ready, failed, or deleted job states. The job response links source metadata, timestamps, errors, and the eventual video id.
Resolve public video metadata including status, title, manifest path, range path, expiration, and created/updated timestamps.
/manifest redirects to the active media-domain manifest. /range
returns segment URLs for a requested start/end sequence window.
Authenticated teams can delete videos and request a source download URL with object metadata such as key, content type, size, and etag.
Early access
Tell us your expected upload volume, library size, and playback pattern. We are shaping the first hosted plans around real workloads.