| title | plannerTaskChatMessage: unsetReaction |
|---|---|
| description | Remove a reaction from a plannerTaskChatMessage for the current user. |
| author | pavlodatsiuk |
| ms.localizationpriority | medium |
| ms.subservice | planner |
| doc_type | apiPageType |
| ms.date | 01/23/2026 |
Namespace: microsoft.graph
[!INCLUDE beta-disclaimer]
Remove a reaction from a plannerTaskChatMessage for the current user.
[!INCLUDE national-cloud-support]
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.
[!INCLUDE permissions-table]
POST /planner/tasks/{task-id}/messages/{message-id}/unsetReaction| Name | Description |
|---|---|
| Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
| Content-Type | application/json. Required. |
In the request body, supply a JSON representation of the reaction to remove.
The following table lists the properties that are required when you remove a reaction.
| Property | Type | Description |
|---|---|---|
| reactionType | String | The type of reaction to remove. For example, like. Required. |
If successful, this method returns a 204 No Content response code.
This method can return any of the HTTP status codes. The most common errors that apps should handle for this method are the 403 and 404 responses. For more information about these errors, see Common Planner error conditions.
The following example shows a request.
POST https://graph.microsoft.com/beta/planner/tasks/01gzSlKkIUSUl6DF_EilrmQAKDhh/messages/5bde7bc8-d998-4e8a-8159-93d4d7ccc3b5/unsetReaction
Content-type: application/json
{
"reactionType": "like"
}[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
The following example shows the response.
HTTP/1.1 204 No Content