AI-generated Key Takeaways
-
This document outlines how to delete a device using an HTTP request, including parameters and expected response.
-
Deleting a device attempts to wipe it, though success is not guaranteed if the device is offline for a long time.
-
Deleted devices will no longer appear in device lists and attempts to retrieve them will return a 404 error.
-
Optional parameters can be used to control device wiping behavior and provide a message for work profile wipes on personal devices.
- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- Try it!
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
calls and a 404 is returned from enterprises.devices.list
.enterprises.devices.get
HTTP request
DELETE https://androidmanagement.googleapis.com/v1/{name=enterprises/*/devices/*}
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
name
|
The name of the device in the form |
Query parameters
| Parameters | |
|---|---|
wipeDataFlags[]
|
Optional flags that control the device wiping behavior. |
wipeReasonMessage
|
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.
Authorization scopes
Requires the following OAuth scope:
-
https://www.googleapis.com/auth/androidmanagement
For more information, see the OAuth 2.0 Overview .
