Exporting Posts
You can export backed-up Microsoft Teams posts.
When you export posts, the request command exports posts to an HTML file and places this file to a temporary folder on the Veeam Backup for Microsoft 365 server. After that, the HTML file is transferred as application/octet-stream media to the client. To download, read, convert to HTML or perform other actions with the octet-stream, use features of programming languages.
|
You can use Swagger UI to download the octet-stream file by clicking the Download action link that server returns in the response body after a successfully completed export operation. For more information, see Evaluation in Swagger UI. |
Request
POST https://<hostname>:4443/v6/RestoreSessions/{restoreSessionId}/organization/teams/{teamId}/posts/export |
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 can specify the following optional properties in the request body:
Property | Type | Description |
|---|---|---|
channelId | string | Specifies the ID of the channel whose posts you want to export. If you specify this property, you can use the from and to properties to specify a time period for which you want to export posts. You do not need to use this property if you use the posts property to specify what posts to export. |
from | UTC | Specifies the point in time that defines the start of the period for which you want to export posts. |
to | UTC | Specifies the point in time that defines the end of the period for which you want to export posts. |
posts | post[] | Accepts IDs of posts that you want to export. The posts must reside in the same channel. You do not need to use this property if you use the channelId property to specify a channel whose posts to export. For more information on how to get such IDs, see Getting Posts. |
Request Example 1
The following example shows how to export the specified posts to an HTML file.
Request Body: { "posts": [ {"id": 1580918830440}, {"id": 1740917436550} ] } |
Request Example 2
The following example shows how to export posts of the specified channel created within the specified time period.
Request Body: { "channelId": "19:94e57dbfaa634f999353b374b69b5800@thread.tacv2", } |
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 following request exports backed-up posts with the IDs 1580918830440 and 1740917436550 to an HTML file.
Request: POST https://abc.tech.local:4443/v6/RestoreSessions/380d7caf738d3d9f-268b-435b-93e2-64e70f8032b6/organization/teams/448c5b66-8dcd-4c75-b636-d3b500bce36f/posts/export
Request Header: Authorization: Bearer <Access-Token>
Request Body: { "posts": [ {"id": 1580918830440}, {"id": 1740917436550} ] }
Response: 200 OK |