Get declaration scope
getDeclarationScopeReport all devices reporting a DDM declaration with status, validity, and grouped failure reasons. Resolves UUIDs to names and serials, noting pending devices are excluded from results.
Instructions
Report every device reporting a given DDM declaration, with its status, validity and — for failures — the reasons Jamf gives, grouped so one cause affecting forty Macs reads as one problem rather than forty. Devices are resolved to names and serials, since the API returns bare UUIDs. The inverse of getDeviceDeclarationState. NOTE: Jamf excludes PENDING declarations from any filtered read and a filter is required, so devices still awaiting delivery are invisible — an all-healthy answer is NOT proof of full deployment. See excludedFromThisAnswer in the result.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| filter | No | RSQL filter. Jamf requires one, so this defaults to "active==true,active==false" — an OR across both boolean values, which is the nearest thing to a match-all this route has. Do NOT use a wildcard like "deviceId==*": wildcards are supported only on declarationIdentifier, which is not filterable here, so that matches nothing and still returns 200. Allowed fields on THIS route: deviceId, channel, lastReportTime, active, validityState, declarationType, dateUpdated. Note declarationIdentifier is NOT among them — it lives in the path here, unlike on getDeviceDeclarationState. | |
| declaration | Yes | The declarationIdentifier, e.g. "Blueprint_FileVault". Exact, not a substring. |