Delete bundle
Namespace: microsoft.graph
Delete a bundle of driveItems by using its id. Deleting a bundle using this method permanently deletes the bundle and doesn't move it to the Recycle Bin. It doesn't, however, remove the items that were referenced by the bundle. They remain in their parent folders.
This API is available in the following national cloud deployments.
Global service | US Government L4 | US Government L5 (DOD) | China operated by 21Vianet |
---|---|---|---|
✅ | ✅ | ✅ | ✅ |
Permissions
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
Permission type | Least privileged permissions | Higher privileged permissions |
---|---|---|
Delegated (work or school account) | Not supported. | Not supported. |
Delegated (personal Microsoft account) | Files.ReadWrite | Files.ReadWrite.All |
Application | Not supported. | Not supported. |
HTTP request
DELETE /drive/items/{bundle-id}
Request headers
Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
if-match | eTag. Optional. If this request header is included and the eTag (or cTag) provided doesn't match the current tag on the bundle, a 412 Precondition Failed response is returned and the bundle won't be deleted. |
Request body
Don't supply a request body for this method.
Response
If successful, this method returns a 204 No Content
response code. It doesn't return anything in the response body.
For information about error responses, see Microsoft Graph error responses and resource types.
Example
Request
The following example shows a request.
DELETE https://graph.microsoft.com/v1.0/drive/items/{bundle-id}
Response
The following example shows the response.
HTTP/1.1 204 No Content
Feedback
https://aka.ms/ContentUserFeedback.
Kommer snart: Under hela 2024 kommer vi att fasa ut GitHub-problem som feedbackmekanism för innehåll och ersätta det med ett nytt feedbacksystem. Mer information finns i:Skicka och visa feedback för