Get a device handling intent
Return the intent behind the DEVICE_HANDLING task of an offboarding ticket: what Primo proposes for each device and accessory of the leaver (recycle, the MDM action on its data, the new owner of a reassignment), whether a return shipment is asked for, and executedAt once executed. Take the intentId from the task (getTicket). devices and accessories have the shape updateDeviceHandlingIntent takes: read them, adjust them, send them there, then executeDeviceHandlingIntent. Refused with INTENT_NOT_FOUND.
Authorizations
Use your Primo API key in the Authorization header as Bearer <API_KEY>.
Path Parameters
Response
Intent id, to pass to its update and execute tools
The typed task that tracks this step
The ticket holding that task, usually the offboarding ticket. Null if it could not be read back.
When the intent executed; null until then
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$