Resend one MDM control's configuration profile to one device
Ask the MDM to deliver an MDM control’s configuration profile to ONE device again — the remediation for a profile the device failed to apply, without re-applying the control to every device it targets. Take mdmControlId from the compliance alert, and call getComplianceAlertDetails first: it reports enforcement.profile.resendable, which is true only when this call would be accepted. A resend is refused when the profile is already being delivered (pending / verifying — wait for the device to check in), and when the control is enforced by a declaration instead of a profile (OS update on Apple, USB blocking on macOS, and the Android controls — those have no per-device redelivery at all). Delivery is asynchronous and needs the device to check in, so it is NOT done when this returns: re-read getComplianceAlertDetails with the same alert id later. Only the profile is resent — to re-run a control’s script use runDeviceScript, to reinstall its software installDeviceSoftware, to re-run its enforcers syncPrimoDevice.
Authorizations
Use your Primo API key in the Authorization header as Bearer <API_KEY>.
Response
Identifier of the configuration profile that was resent
Delivery status of the profile on the device just before the resend was requested
verified, verifying, pending, failed A human-readable description of the action