Execute third party camera discovery
Trigger a discovery of cameras on the local LANs
Authorizations
Your Rhombus API key. Must be accompanied by the x-auth-scheme header set to api-token (or partner-api-token for partner endpoints).
Headers
Authentication scheme identifier. Use api-token for standard API key authentication, partner-api-token for partner API key authentication. Must be paired with the x-auth-apikey header containing your API key.
api-token, api, partner-api-token, partner-api Body
Request object for executing third-party camera discovery.
Optional list of additional IPv4 CIDRs (e.g. "10.5.0.0/24") to scan for cameras on routed subnets that the NVR is not directly attached to. When empty (the default), discovery only covers the NVR's own directly-attached subnets. Multicast/WS-Discovery cannot cross routers, so these subnets are covered by an RTSP port scan followed by unicast ONVIF probes. At most 8 entries, each /16 or smaller.
Optional list of additional IPv4 CIDRs (e.g. "10.5.0.0/24") to scan for cameras on routed subnets that the NVR is not directly attached to. When empty (the default), discovery only covers the NVR's own directly-attached subnets. Multicast/WS-Discovery cannot cross routers, so these subnets are covered by an RTSP port scan followed by unicast ONVIF probes. At most 8 entries, each /16 or smaller.
Set of device UUIDs to filter discovery by
base 64 (url-safe) uuid string
"AAAAAAAAAAAAAAAAAAAAAA"
Set of location UUIDs to filter discovery by
base 64 (url-safe) uuid string
"AAAAAAAAAAAAAAAAAAAAAA"
Response
OK