Skip to main content

Overview

Rhombus cameras expose multiple ways to access video content through the public API:
  • Live streaming for real-time monitoring, embedded as a Rhombus-hosted iframe
  • HLS manifests (.m3u8) for direct playback in your own player
  • Thumbnail images for dashboards and quick previews
  • Frame captures at any historical timestamp
For downloading recorded footage as MP4 files, see Recorded Video Access.

Getting Camera Thumbnails

All Rhombus cameras automatically upload thumbnail images. These are perfect for dashboards, monitoring interfaces, and quick status checks.

Thumbnail Endpoint

Retrieve camera thumbnails using a GET request to:
All media.rhombussystems.com endpoints use the same authentication as the main API — include the x-auth-scheme and x-auth-apikey headers on every request.
To get the cameraUuid and mediaRegion for a camera, call POST /api/camera/getMinimalCameraStateList. The response contains a cameraStates array; each entry has uuid and mediaRegion fields.

Basic Implementation

cURL
cURL

Getting Frames at Specific Times

To get a JPEG image at a specific historical timestamp, call POST /api/video/getExactFrameUri. The response contains a frameUri — make a GET request to that URI with the same authentication headers to download the frame.
The request also accepts optional downscaleFactor, jpgQuality, and permyriadCropX/permyriadCropY/permyriadCropWidth/permyriadCropHeight fields (each in 1/10000ths of the image dimensions, where 10000 = 100%).

Live Video Streaming

Rhombus offers two ways to play live video in your application:
  1. Embed the Rhombus player as an iframe — easiest path; analytics and timeline events render automatically.
  2. Play the HLS manifest directly — use your own player (hls.js, Safari native, etc.) for full UI control.
Both come from the same API call: POST /api/camera/createSharedLiveVideoStream. The response contains both URLs: Create a shared stream, then drop the returned URL into an iframe. The iframe player handles authentication via the URL itself, so no API key is needed in the browser.
Embed the returned URL:

React Component Example

URL Parameters for Enhanced Control

Customize the embedded player with URL parameters. All parameters can be set to true or false:

Parameter Usage

Append parameters to the shared stream URL: https://{{url}}/?{{variable}}=true&{{variable}}=false Example:

React Usage with Parameters

Embedding HLS Streams Directly

If you want to render live video in your own player rather than the hosted iframe, use sharedLiveM3U8StreamUrl from the same createSharedLiveVideoStream response. The manifest is a standard HLS .m3u8 and is signed with a token in the URL itself — no x-auth-apikey header is needed when fetching it.
The HLS URL is single-org-scoped and time-limited. Treat it as a credential and don’t expose it in public-facing pages without an expiration policy.
Safari plays HLS natively. For other browsers, use hls.js:
Because creating a shared stream requires an API key, do the createSharedLiveVideoStream call from a server you control and pass only the resulting sharedLiveM3U8StreamUrl (or sharedLiveVideoStreamUrl) to the browser. Keep the API key out of client code.

Recorded Video Access

To export recorded footage as a clip, use the public clip API. Clip creation is asynchronous:
  1. Call POST /api/video/spliceV3 with the cameras and time range you want. Provide deviceUuids (array), startTimeMillis (epoch milliseconds), and durationSec. Set audioIncluded: true to mux in audio from an associated audio gateway. The response returns a clipUuid.
  2. Poll POST /api/event/getClipsWithProgress to track processing — each clip reports percentComplete and status — and retrieve the finished clip once it is ready.
cURL
cURL
As a convenience, the Rhombus CLI can also download footage without wiring up this flow yourself:
For alert-driven workflows, configure a webhook to deliver alert events to your service, then create a clip for the alert’s time range. To list recent alerts programmatically, use POST /api/event/getPolicyAlerts — the previous getPolicyAlertsV2 endpoint is deprecated.

Complete Implementation Example

A React component supporting both thumbnail and live-stream view types:

Usage Examples

Best Practices

Performance Optimization

  • Thumbnail caching: Cache thumbnails client-side and refresh on a sensible interval rather than polling continuously.
  • Lazy loading: Load video content only when needed or when in viewport.
  • Quality selection: Use lowRes=true on the iframe player for grids and dashboards.

Security Considerations

  • Keep API keys server-side: Never expose x-auth-apikey in browser code. Call createSharedLiveVideoStream from your backend and pass only the resulting URLs to the client.
  • HTTPS only: Always use HTTPS for API calls and shared stream URLs.
  • Scope keys narrowly: Limit each API key to the minimum permissions required.
  • Set expirations on shared streams: Pass expirationTimeSecs when creating shared streams so URLs don’t outlive the use case.

Error Handling

Accessibility

Troubleshooting

Thumbnail not loading
  • Verify cameraUuid and mediaRegion came from a recent getMinimalCameraStateList response — mediaRegion can change.
  • Check that the API key has access to the camera’s location.
  • Confirm the camera is online (connectionStatus in the camera state response).
Stream connection failures
  • Check network connectivity to *.rhombussystems.com.
  • For HLS playback, confirm the browser supports HLS natively or that hls.js is loaded.
  • Inspect firewall/proxy rules — corporate proxies frequently block media segment requests.
Poor video quality
  • Pass lowRes=true for bandwidth-constrained clients.
  • Check upstream bandwidth at the camera site.

Next Steps

Video Player

Build a custom video player with HLS playback and timeline controls.

LAN Realtime Detection

Parse AI bounding boxes from the LAN H.264 WebSocket stream and overlay them on live video.

Backup Footage

Download and archive camera footage to local storage.
Last modified on July 8, 2026