Needs attention report

Retrieve a report containing devices that need attention. See Using Global API Keys for more information on permission and scope requirements.

SecuritybearerAuth
Request
query Parameters
o
required
integer <int64>

Organization ID. The organization will be assumed based on the API key, if not specified.

Example: o=123456
groupId
integer <int64>

Group ID. If omitted, results will include all groups for the authenticated user.

Example: groupId=123456
limit
integer >= 1
Default: 250

Limit number of results returned per page. Typically used in combination with offset

offset
integer
Default: 250

Specifies the offset. For example, if you are paging 250 at a time, you could specify 250 for the 2nd page and 500 for the 3rd, etc.

Responses
200

Successful Operation

400

Invalid Request

401

Access token is missing or invalid

403

You do not have permission to perform this action.

404

Entity not found

429

Too many requests

503

Service Unavailable

default

Invalid Request

get/reports/needs-attention
Request samples 
$apiKey = 'your_automox_api_key'
$headers = @{ "Authorization" = "Bearer $apiKey" }
$url = 'https://console.automox.com/api/reports/needs-attention?o=0000&groupId=12345&limit=10&offset=20'
$response = (Invoke-WebRequest -Method Get -Uri $url -Headers $headers).Content
Response samples
application/json
{
  • "summary": "Needs attention example",
  • "description": "Example of devices that need attention, showing compliance status and vulnerability severity counts",
  • "value": {
    • "nonCompliant": {
      • "total": 0,
      • "no_known_cves": 0,
      • "unknown": 0,
      • "none": 0,
      • "low": 0,
      • "medium": 0,
      • "high": 0,
      • "critical": 0,
      • "devices": [ ]
      }
    }
}