message: replyAll

Reply to all recipients of a message by specifying a comment and modifying any updateable properties for the reply, all by using the replyAll method. The message is then saved in the Sent Items folder.

Alternatively, you can first create a draft reply-all message to include a comment or update any message properties, and then send the reply.

Note

  • You can specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.
  • If the replyTo property is specified in the original message, per Internet Message Format (RFC 2822), you should send the reply to the recipients in the
    replyTo and toRecipients properties, and not the recipients in the from and toRecipients properties.

Prerequisites

One of the following scopes is required to execute this API: Mail.Send

HTTP request

POST /users/me/messages/{id}/replyAll
POST /users/{id | userPrincipalName}/messages/{id}/replyAll
POST /me/mailFolders/{id}/messages/{id}/replyAll
POST /users/{id | userPrincipalName}/mailFolders/{id}/messages/{id}/replyAll

Request headers

Name Type Description
Authorization string Bearer . Required.
Content-Type string Nature of the data in the body of an entity. Required.

Request body

In the request body, provide a JSON object with the following parameters.

Parameter Type Description
comment String A comment to include. Can be an empty string.
message message Any writeable properties to update in the reply message.

Response

If successful, this method returns 202, Accepted response code. It does not return anything in the response body.

Example

The following example includes a comment and adds an attachment to the reply-all message.

Request

Here is an example of the request.

POST https://graph.microsoft.com/beta/me/messages/AAMkADA1MTAAAH5JaKAAA=/replyAll
Content-Type: application/json

{
    "message":{
      "attachments": [ 
        { 
          "@odata.type": "#microsoft.graph.fileAttachment", 
          "name": "guidelines.txt", 
          "contentBytes": "bWFjIGFuZCBjaGVlc2UgdG9kYXk=" 
        } 
      ]
    },
    "comment": "Please take a look at the attached guidelines before you decide on the name." 
}
Response

Here is an example of the response.

HTTP/1.1 202 Accepted