You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/references-work-with-defender-for-iot-apis.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2693,7 +2693,7 @@ This API returns data about all devices that were updated after the given timest
2693
2693
2694
2694
#### Query parameters
2695
2695
2696
-
-**sensorId** - use this parameter to get only devices seen by a specific sensor. The ID should be taken from the results of the Sensors API.
2696
+
-**sensorId** - use this parameter to get only devices seen by a specific sensor. The ID should be taken from the results of the [sensor](#request-sensor-data---externalv3integrationsensors) API.
2697
2697
-**notificationType** - should be a number, from the following mapping:
2698
2698
-**0** – both updated and new devices (default).
2699
2699
-**1** – only new devices.
@@ -2894,7 +2894,7 @@ This API returns data about device CVEs after the given timestamp.
2894
2894
2895
2895
-**JSON**
2896
2896
2897
-
#### Response structure
2897
+
#### Response structure
2898
2898
2899
2899
-**u_count** - amount of objects in the full result sets, including all pages.
2900
2900
-**u_id** - the same as in the specific device API.
0 commit comments