PATCH /communications/onlineMeetingConversations/{onlineMeetingEngagementConversation-id}/messages/{engagementConversationMessage-id}/replies/{engagementConversationMessage-id1}/reactions/{engagementConversationMessageReaction-id}
Update the navigation property reactions in communicationsServers
- https://graph.microsoft.com/v1.0
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
engagementConversationMessage-id1 |
String | Yes |
The unique identifier of engagementConversationMessage |
engagementConversationMessageReaction-id |
String | Yes |
The unique identifier of engagementConversationMessageReaction |
engagementConversationMessage-id |
String | Yes |
The unique identifier of engagementConversationMessage |
onlineMeetingEngagementConversation-id |
String | Yes |
The unique identifier of onlineMeetingEngagementConversation |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.