Device and edge video APIs

Choose between communicating with device services and deploying an application on the device. Check permissions, deployment requirements and product support for that approach.

On this page

Overview#

Vendor APIs / Device and edge video

Device APIs sit close to sensors, relays, microphones, credentials, firmware, and evidence. Treat discovery or video read access separately from configuration, account administration, PTZ, audio, door release, output control, application installation, and firmware operations.

Pages#

Architecture choice#

Need	Prefer when supported	Main review question
Fleet neutral discovery/media	Declared ONVIF or other standard profile	Does the exact model have a valid conformance declaration and required conditional features?
Vendor specific configuration or events	Native HTTPS API	Can the integration discover API/version capabilities rather than infer them from model name?
High throughput native media/client integration	Vendor SDK	Which package version, runtime, architecture, codec licence, and product builds are supported?
Analytics or business logic on device	Supported edge application framework	What are signing, sandboxing, resources, upgrade, permission, and rollback contracts?
Intercom/access actuation	Narrow native service with least privilege	What independent authorisation and physical safety controls protect the command?

Minimum device record#

Record vendor, model, hardware revision, firmware/OS, enabled API family and version, advertised capabilities, TLS and identity state, time source, roles, licences, installed edge apps, app signatures, resource limits, and rollback path. Don't enable legacy HTTP or broad administrator access merely because an old integration sample uses it.

Related foundations: media streaming, TLS and PKI, multicast and discovery, and secure commissioning.

Section overview · Wiki home