StreamPlume Developers

Everything you need to upload, package and deliver adaptive video from your own application — REST API, signed playback, SDKs and delivery telemetry.

Quickstart

Upload your first asset and get a playable manifest in about five minutes.

HTTP API

Endpoints for assets, renditions, playback tokens and delivery reports.

SDKs

Official clients for Node, Python and Go, plus a thin REST wrapper for everything else.

Player demo

A working HLS ladder served from this origin, with the segment layout we use in production.

Webhooks

Asset lifecycle events delivered to your endpoint with signed payloads.

Delivery status

Live health of ingest, packaging and edge delivery components.

How delivery works

An upload is transcoded into an adaptive ladder, packaged as HLS and published to a delivery origin. Player requests hit the nearest edge, which pulls segments from the origin on a cache miss and keeps them warm for subsequent viewers.

# the shape of a published asset
/video/hls/<ladder>/master.m3u8      # multivariant manifest
/video/hls/<rung>/index.m3u8         # media playlist per rendition
/video/hls/<rung>/part.ts            # transport-stream segments

Segment paths are stable for the lifetime of an asset. Cache them freely at the edge, but always fetch manifests with a short TTL so ladder changes are picked up.

Base URL

https://api.streamplume.com/v1

All requests require a bearer token. Keys are scoped per project and can be rotated without downtime — see the API reference.