Skip to main content
PUT
/
compliance
/
alert-rules
/
{ruleId}
Update a compliance alert rule
curl --request PUT \
  --url https://api.getprimo.com/compliance/alert-rules/{ruleId} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "nonCompliantStatus": []
}
'
{
  "rule": {
    "id": "<string>",
    "nonCompliantStatus": [],
    "config": {},
    "createdAt": "2023-11-07T05:31:56Z",
    "updatedAt": "2023-11-07T05:31:56Z"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.getprimo.com/llms.txt

Use this file to discover all available pages before exploring further.

Key: Write Scope: Company

Authorizations

​
Authorization
string
header
required

Use your Primo API key in the Authorization header as Bearer <API_KEY>.

Path Parameters

​
ruleId
string
required

Body

application/json
​
nonCompliantStatus
enum<string>[]
required

Non-compliant device statuses that should trigger an alert for this rule. Only non-compliant statuses are accepted (compliant statuses like SUCCESS, ONLINE, ENCRYPTED, etc. are rejected). Pass an empty array to disable alerts.

Available options:
ACTIVE,
NOT_PROTECTED,
OFFLINE_7_DAYS,
PENDING,
PROTECTED,
FAILED,
NOT_ENCRYPTED,
MISSING_RECOVERY_KEY,
ENCRYPTED,
ACTION_REQUIRED,
GRACE_PERIOD,
UP_TO_DATE,
NOT_UP_TO_DATE,
ENFORCED,
ERROR,
CREATION_PENDING,
DEMOTION_PENDING,
CREATED,
CREATION_FAILED,
SUCCESS,
INSTALLED,
MDM_ON,
MDM_OFF,
MDM_ON_IN_ANOTHER_MDM,
READY_ZTD,
MISSING_AGENT,
ONLINE,
OFFLINE,
ENABLED,
DISABLED,
MISSING_BYPASS_CODE,
MEETS_REQUIREMENTS,
BELOW_MINIMUM_VERSION,
UNSUPPORTED_OS_EDITION

Response

default - application/json
​
rule
object
required