Sending Posts

In this article

You can send a backed-up Microsoft Teams post with the specified ID as an attachment in an email message.

Request

POST https://<hostname>:4443/v6/RestoreSessions/{restoreSessionId}/organization/teams/{teamId}/posts/{postId}/send

Request Headers

The request header must contain an authorization token of the current session.

Request Parameters

The following parameters must be specified in the URL of the request:

Parameter	Type	Description
restoreSessionId	string	Specifies the identification number of the restore session. For more information on how to get this parameter, see Getting Restore Sessions.
teamId	string	Specifies the identification number of the team. For more information on how to get this parameter, see Getting Teams.
postId	string	Specifies the identification number of the post. For more information on how to get this parameter, see Getting Posts.

Request Body

The request body must contain the following properties:

Property	Type	Description
from	string	Specifies the email address from which the restored post will be sent.
to	string	Specifies the email address to which the restored post will be sent.
subject	string	Specifies the subject of the email message used for sending the restored post.
text	string	Specifies the body of the email message used for sending the restored post.

For example:

Request Body:

{

"from": "admin@tech.com",

"to": "user@tech.com",

"subject": "teams restore",

"text": "sent by rest api"

}

Sending Posts Note

If you omit the from property, the default sender email address specified in Veeam Explorer for Microsoft Teams email settings will be used. To specify Veeam Explorer for Microsoft Teams email settings, send the PUT HTTPS request to the /VETEmailSettings URL. For more information, see Editing Notification Settings.

Response

The server returns the following response to the client.

Response Codes

A successfully completed operation returns a response code 200 OK.

Response Headers

The response to this request contains the following headers. The response may also include additional standard HTTPS headers.

Header	Description
Content-length	The length of the response body.
Content-type	The media type and syntax of the response body message for the requests with the export and save actions: application/octet-stream. The media type and syntax of the response body message for the requests with the restore and send actions: null.

Header

Description

Content-length

The length of the response body.

Content-type

The media type and syntax of the response body message for the requests with the export and save actions: application/octet-stream.

The media type and syntax of the response body message for the requests with the restore and send actions: null.

Response Body

None.

Example

The following request sends a backed-up post with the ID 1603973537508 as an attachment in an email message.

Request:

POST https://abc.tech.local:4443/v6/RestoreSessions/380d7caf738d3d9f-268b-435b-93e2-64e70f8032b6/organization/teams/448c5b66-8dcd-4c75-b636-d3b500bce36f/posts/1603973537508/send

Request Header:

Authorization: Bearer <Access-Token>

Request Body:

{

"from": "admin@tech.com",

"to": "user@tech.com",

"subject": "teams restore",

"text": "sent by rest api"

}

Response:

200 OK