Deletes a device. This operation attempts to wipe the device but this is not guaranteed to succeed if the device is offline for an extended period. Deleted devices do not show up in enterprises.devices.list calls and a 404 is returned from enterprises.devices.get.
Optional flags that control the device wiping behavior.
wipeReasonMessage
string
Optional. A short message displayed to the user before wiping the work profile on personal devices. This has no effect on company owned devices. The maximum message length is 200 characters.
Request body
The request body must be empty.
Response body
If successful, the response body is an empty JSON object.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-25 UTC."],[[["Permanently deletes a device, wiping its data and removing it from enterprise device lists."],["The wipe behavior can be customized using optional flags like `wipeDataFlags` and `wipeReasonMessage`."],["Requires authorization with the `https://www.googleapis.com/auth/androidmanagement` scope."],["The request body should be empty, and a successful deletion results in an empty response body."],["Device deletion uses the `DELETE` method with the device name as a path parameter."]]],["This document outlines the process for deleting a device via a `DELETE` HTTP request to the specified URL, requiring an empty request body. The device name is provided as a path parameter. Optional query parameters include `wipeDataFlags`, for managing data wiping behavior, and `wipeReasonMessage`, a user-facing message for personal devices. Successful deletion returns an empty JSON object. Deletion also involves wiping the device and removing it from device lists. Authentication requires the `androidmanagement` OAuth scope.\n"]]
