Saving Posts

You can save backed-up Microsoft Teams posts.

When you save posts, the request command saves posts to MSG files and places the files to a temporary folder on the Veeam Backup for Microsoft 365 server. After that, the files are transferred as application/octet-stream media to the client. To download, read or perform other actions with the octet-stream, use features of programming languages.

Saving Posts Tip

You can use Swagger UI to download data from the stream by clicking the Download action link in the response body. For more information, see Evaluation in Swagger UI.

Request

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

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.

Request Body

You must specify one of the following properties in the request body:

Property

Type

Description

channelId

string

Specifies the ID of the channel whose posts you want to save. Veeam Explorer for Microsoft Teams will save all posts of this channel.

You do not need to use this property if you use the posts property to specify what posts to save.

posts

posts[]

Specifies the IDs of posts that you want to save. The posts must reside in the same channel. For more information on how to get such IDs, see Getting Posts.

You do not need to use this property if you use the channelId property to specify a channel whose posts to save.

For example:

Request Body:

{

   "posts": [

    {"postId": 1580918830440},

    {"postId": 1740917436550}

    ]

}

Response

The server returns the following response to the client.

Response Codes

A successfully completed operation returns 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.

Response Body

In the response body, the server returns binary data stream.

Example

The example shows how to save backed-up posts with the IDs 1580918830440 and 1740917436550.

Request:

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

 

Request Header:

Authorization: Bearer <Access-Token>

 

Request Body:

{

   "posts": [

    {"postId": 1580918830440},

    {"postId": 1740917436550}

    ]

}

 

Response:

200 OK