[Developers]

Stream Domain

A tactical operations commander wants live video from three body-worn cameras and a drone feed displayed simultaneously on the command post screen during a search operation. At the same time, a digital forensic examiner

Category: Api DomainsLast Updated: Feb 5, 2026
api-domainsreal-time

Overview#

A tactical operations commander wants live video from three body-worn cameras and a drone feed displayed simultaneously on the command post screen during a search operation. At the same time, a digital forensic examiner needs to upload 40 GB of dashcam footage as evidence and generate a signed playback URL for the reviewing detective. Both workflows run through the Stream domain: it handles direct video upload, URL-based ingestion, live streaming endpoint management, and the generation of time-limited signed URLs that control who can play a video and for how long. Chain of custody is maintained across every asset.

Key Features#

  • Video Upload: Upload video files directly or by providing source URLs, with automatic processing and transcoding for optimal playback across devices and network conditions.

  • Secure Playback: Generate time-limited signed playback URLs that control who can view video content and for how long, ensuring evidence videos are only accessible to authorised personnel.

  • Live Streaming: Create and manage live streaming endpoints that support multiple streaming protocols, enabling real-time video feeds from field operations, surveillance cameras, and other sources.

  • Video Clipping: Extract specific segments from longer videos to create clips of relevant footage, useful for isolating key moments in evidence videos or creating briefing materials.

  • Video Management: Organise, search, and manage video assets with metadata, tags, and lifecycle controls including retention policies and access permissions.

  • Multi-Protocol Support: Deliver video content through multiple streaming protocols to ensure compatibility with a wide range of playback devices and network environments.

Use Cases#

Video management with chain of custody controls applies wherever video evidence must be stored, shared, or streamed securely. Key industries include law enforcement and criminal justice, defence and military operations, and corporate security.

  • Evidence Video Management: Upload, store, and securely share video evidence with chain of custody controls and time-limited access for legal proceedings.

  • Live Operational Feeds: Stream real-time video from field operations, surveillance systems, and body-worn cameras to command centres and authorised viewers.

  • Incident Documentation: Capture and clip relevant video segments from live streams or recorded footage to document incidents as they unfold.

  • Briefing Materials: Create video clips that highlight key moments for use in briefings, training materials, and presentation packages.

Integration#

The Stream domain supports video workflows across the platform:

  • Evidence Management: Video uploads link to evidence records with integrity verification
  • Surveillance: Live camera feeds are managed through the streaming infrastructure
  • Investigation Management: Video assets are associated with active investigations
  • Sharing: Secure playback links enable controlled video distribution

Open Standards#

  • HTTP Live Streaming (HLS / IETF RFC 8216): Video playback is delivered via HLS manifest (.m3u8) URLs, enabling adaptive bitrate streaming across all HLS-compatible players and devices.
  • MPEG-DASH (ISO/IEC 23009-1): Alongside HLS, DASH playback URLs are exposed so clients can select the appropriate adaptive streaming format for their environment.
  • JSON Web Token (RFC 7519): Time-limited signed playback URLs are issued as JWTs (RS256, with sub, kid, and exp claims) to enforce who can view a video and for how long.
  • Real-Time Messaging Protocol Secure (RTMPS): Live streaming inputs accept ingest via RTMPS, the encrypted variant of RTMP, making the platform compatible with broadcast encoders and body-worn camera firmware that targets this protocol.
  • Secure Reliable Transport (SRT): Live inputs additionally expose an SRT ingest endpoint with stream ID and passphrase, supporting low-latency, loss-tolerant transmission from field cameras and drones over unreliable networks.
  • WebRTC (W3C / IETF RFC 8825 suite): A WebRTC ingest URL is provisioned on each live input, enabling ultra-low-latency browser and mobile contributions without dedicated encoding hardware.
  • TUS Resumable Upload Protocol (tus.io v1.0): Direct creator upload URLs honour TUS resumable upload semantics, so large evidence video files can survive interrupted connections without restarting from scratch.
  • OAuth 2.0 Bearer Token (RFC 6750): All API calls to the streaming service are authenticated via a Bearer token in the Authorization header, consistent with the platform-wide OAuth 2.0 security model.

Last Reviewed: 2026-02-05 Last Updated: 2026-04-14

Ready to Build?

Get started with our APIs or contact our integration team for support.