Integrate in a SaaS

Scope and prerequisites

Show cameras inside your SaaS by tenant, site, and role. The platform supplies the device list and play credentials. Your service decides who can see which camera. Do not replace the integration with a deep link into the consumer app.

Steps

1. Register and create an app. Store the AppSecret separately per environment.
2. Bind cameras to the developer account. Visibility in the consumer app does not mean OpenAPI can list them.
3. Call accessToken on the BFF and cache it. Do not return that token to the browser.
4. Call Paged device detail and store deviceId and channel in your site data. pageSize is 1–50.
5. When a user opens one camera, check tenant, site, and role first. If the check fails, return a generic denial. Do not reveal whether that camera exists for another tenant, and do not call a play API. After the check passes, mint credentials: getKitToken for the web, bindDeviceLive or createDeviceRtmpLive for a live address, or OpenSDK for a native app. Record who watched which camera in your own audit log. Open Platform only answers whether this developer app may operate the bound cameras.

Client implementations

Web playback is in Integrate on the web. Live addresses are in Cloud live from an AppId. Packages are in Downloads.

Do not open every HD stream at login. Start a stream when a cell is visible, and default to SD (streamId 1).

Related reference

• Integrate a camera
• Sub-accounts and policies