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.
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.
The request header must contain an authorization token of the current session.
The following parameters must be specified in the URL of the request:
Specifies the identification number of the restore session. For more information on how to get this parameter, see Getting Restore Sessions.
Specifies the identification number of the team. For more information on how to get this parameter, see Getting Teams.
You must specify one of the following properties in the request body:
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.
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.
The server returns the following response to the client.
A successfully completed operation returns response code 200 OK.
The response to this request contains the following headers. The response may also include additional standard HTTPS headers.
The length of the response body.
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.
In the response body, the server returns binary data stream.
The example shows how to save backed-up posts with the IDs 1580918830440 and 1740917436550.
Authorization: Bearer <Access-Token>