Understand how devices, events, media, and embeds fit together.
Use this page to choose the right integration boundary before you implement anything large. The platform is easiest to work with when you separate device state, event delivery, playback, and application-level access control.
Core layers
- Devices publish operational status, events, and media metadata.
- Edge and ingest services normalize streams and event payloads.
- Cloud APIs expose inventory, event history, retention policy, and access-aware playback metadata.
- Webhook delivery sends low-latency event notifications into your downstream systems.
- UI Embed renders ready-made player and review surfaces inside your application.
Recommended integration models
Pull-first model
Use Cloud API polling for admin dashboards, daily reconciliation jobs, and moderate-latency operator workflows.
Push-first model
Use Webhooks for motion alerts, clip creation, and operational automation that needs near real-time delivery.
Device -> Ingest -> Event bus -> Webhook delivery
\-> Media policy -> Player session -> UI Embed
Media and playback boundaries
Keep streaming authorization separate from your business logic. Let the platform issue short-lived playback sessions while your own app decides who should be able to request them.
If you model tenants, sites, and roles cleanly in your own system, embed and playback flows stay much simpler later.
Implementation sequence
- Start with Getting Started.
- Add inventory and state reads from Cloud API.
- Layer in Webhooks for event-driven behavior.
- Use UI Embed when you need production-ready camera views.