Find discoveries with unassigned RTSP endpoints

Finds discoveries that have unassigned RTSP endpoints. Only discoveries containing at least one endpoint are returned.

POST /api/relay/findDiscoveriesWithUnassignedRtspEndpoints

Find discoveries with unassigned RTSP endpoints

cURL

curl --request POST \
  --url https://api2.rhombussystems.com/api/relay/findDiscoveriesWithUnassignedRtspEndpoints \
  --header 'Content-Type: application/json' \
  --header 'x-auth-apikey: <api-key>' \
  --header 'x-auth-scheme: <x-auth-scheme>' \
  --data '{}'

200

{
  "discoveries": [
    {
      "codec": "H.264",
      "ipAddress": "192.168.1.100",
      "macAddress": "<string>",
      "manufacturer": "Hikvision",
      "model": "DS-2CD2142FWD-I",
      "orgUuid": "AAAAAAAAAAAAAAAAAAAAAA",
      "unassignedRtspEndpoints": [
        {
          "password": "password123",
          "rtspUrl": "rtsp://192.168.1.100:554/stream1",
          "username": "admin",
          "uuid": "AAAAAAAAAAAAAAAAAAAAAA"
        }
      ]
    }
  ]
}

Authorizations

x-auth-apikey · string · header · required

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

x-auth-scheme · enum<string> · default: api-token · required

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.

Available options: api-token, api, partner-api-token, partner-api

Body

application/json

Request object for finding discoveries with unassigned RTSP endpoints.

Response

200 - application/json

OK

Response object containing discoveries with unassigned RTSP endpoints.

discoveries · object[] | null

List of discoveries with unassigned RTSP endpoints

Show child attributes