Getting Teams

In this article

    This section explains how to get a resource representation of a backed-up team with the specified ID.

    Request

    GET https://<hostname>:4443/v5/RestoreSessions/{restoreSessionId}/organization/teams/{teamId}

    Request Headers

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

    Request Body

    None.

    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: application/json; charset=utf-8

    Response Body

    In the response body, the server returns a resource representation of the /RestoreSessions/{restoreSessionId}/organization/teams/{teamId} resource. The response body contains the following parameters:

    Property

    Type

    Description

    id

    string

    ID of the backed-up team.

    displayName

    string

    Display name of the backed-up team.

    description

    string

    Description of the backed-up team.

    groupEmail

    site

    Email address of the backed-up team.

    alias

    string

    Alias of the backed-up team.

    privacy

    string

    Type of the team: Public, Private or Org-Wide.

    isArchived

    boolean

    Defines whether the team is archived.

    _links

    Dictionary of string [key] and Object [value]

    Links to related resources (navigation property).

    Example

    The following request returns a resource representation of a backed-up with the ID 448c5b66-8dcd-4c75-b636-d3b500bce36f.

    Request:

    GET https://abc.tech.local:4443/v5/RestoreSessions/1016c007-fe65-4f25-9d71-cc7ea387b3dc/organization/teams/448c5b66-8dcd-4c75-b636-d3b500bce36f

     

    Request Header:

    Authorization: Bearer <Access-Token>

     

    Response:

    200 OK

     

    Response Body:

    {

     "id": "448c5b66-8dcd-4c75-b636-d3b500bce36f",

     "displayName": "IT&Finance",

     "description": "IT&Finance",

     "groupEmail": "IT&Finance@abc.onmicrosoft.com",

     "alias": "IT&Finance",

     "privacy": "Public",

     "isArchived": false,

     "_links": {

       "self": {

         "href": "https://abc.tech.local:4443/v5/RestoreSessions/1016c007-fe65-4f25-9d71-cc7ea387b3dc/organization/teams/448c5b66-8dcd-4c75-b636-d3b500bce36f"

       },

       "channels": {

         "href": "https://abc.tech.local:4443/v5/RestoreSessions/1016c007-fe65-4f25-9d71-cc7ea387b3dc/organization/teams/448c5b66-8dcd-4c75-b636-d3b500bce36f/channels"

       }

     }

    }

    I want to report a typo

    There is a misspelling right here:

     

    I want to let the Veeam Documentation Team know about that.