Delete attachment
Namespace: microsoft.graph
Important
APIs under the /beta
version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.
Caution
Existing apps that use this feature with Outlook tasks should be updated, as Outlook tasks are being deprecated. See To Do APIs in public preview for more information.
Delete an attachment from a user calendar event, message, Outlook task, or post.
This API is available in the following national cloud deployments.
Global service | US Government L4 | US Government L5 (DOD) | China operated by 21Vianet |
---|---|---|---|
✅ | ✅ | ✅ | ✅ |
Permissions
Depending on the resource (event, message, outlookTask, or post) that the attachment is attached to and the permission type (delegated or application) requested, the permission specified in the following table is the least privileged required to call this API. To learn more, including taking caution before choosing more privileged permissions, search for the following permissions in Permissions.
Supported resource | Delegated (work or school account) | Delegated (personal Microsoft account) | Application |
---|---|---|---|
event | Calendars.ReadWrite | Calendars.ReadWrite | Calendars.ReadWrite |
message | Mail.ReadWrite | Mail.ReadWrite | Mail.ReadWrite |
outlookTask | Tasks.ReadWrite | Tasks.ReadWrite | Not supported |
post | Group.ReadWrite.All | Not supported | Not supported |
HTTP request
Attachments for an event in the user's default calendar.
DELETE /me/events/{id}/attachments/{id}
DELETE /users/{id | userPrincipalName}/events/{id}/attachments/{id}
DELETE /me/calendar/events/{id}/attachments/{id}
DELETE /users/{id | userPrincipalName}/calendar/events/{id}/attachments/{id}
Attachments for an event in the specified calendar that belongs to the user.
DELETE /me/calendars/{id}/events/{id}/attachments/{id}
DELETE /users/{id | userPrincipalName}/calendars/{id}/events/{id}/attachments/{id}
Attachments for an event in a calendar that belongs to the user's default calendarGroup.
DELETE /me/calendars/{id}/events/{id}/attachments/{id}
DELETE /users/{id | userPrincipalName}/calendars/{id}/events/{id}/attachments/{id}
Attachments for an event in a calendar that belongs to a user's calendarGroup.
DELETE /me/calendarGroups/{id}/calendars/{id}/events/{id}/attachments/{id}
DELETE /users/{id | userPrincipalName}/calendarGroups/{id}/calendars/{id}/events/{id}/attachments/{id}
Attachments for a message in a user's mailbox.
DELETE /me/messages/{id}/attachments/{id}
DELETE /users/{id | userPrincipalName}/messages/{id}/attachments/{id}
Attachments for a message contained in a top level mailFolder in a user's mailbox.
DELETE /me/mailFolders/{id}/messages/{id}/attachments/{id}
DELETE /users/{id | userPrincipalName}/mailFolders/{id}/messages/{id}/attachments/{id}
Attachments for a message contained in a child folder of a mailFolder in a user's mailbox. The following example shows one level of nesting, but a message can be located in a child of a child and so on.
DELETE /me/mailFolders/{id}/childFolders/{id}/.../messages/{id}/attachments/{id}
DELETE /users/{id | userPrincipalName}/mailFolders/{id}/childFolders/{id}/messages/{id}/attachments/{id}
Attachments for an Outlook task.
DELETE /me/outlook/tasks/{id}/attachments/{id}
DELETE /users/{id}/outlook/tasks/{id}/attachments/{id}
Attachments for a post in a thread that belongs to a conversation of a group.
DELETE /groups/{id}/threads/{id}/posts/{id}/attachments/{id}
DELETE /groups/{id}/conversations/{id}/threads/{id}/posts/{id}/attachments/{id}
Request headers
Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
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.
Example
Request
The following example shows a request to delete an attachment on an event.
DELETE https://graph.microsoft.com/beta/me/events/{id}/attachments/{id}
Response
The following example shows the response.
HTTP/1.1 204 No Content
意見反應
https://aka.ms/ContentUserFeedback。
即將登場:在 2024 年,我們將逐步淘汰 GitHub 問題作為內容的意見反應機制,並將它取代為新的意見反應系統。 如需詳細資訊,請參閱:提交並檢視相關的意見反應