Getting Teams Data by Repository and Team ID

In this article

    This section explains how to get a backed-up team with the specified ID whose data is stored in a backup repository with the specified ID.

    Request

    GET https://<hostname>:4443/v5/BackupRepositories/{repositoryId}/TeamData/{teamId}

    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

    repositoryId

    string

    Identification number of the backup repository.

    teamId

    string

    Identification number of the team.

    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

    Property

    Type

    Description

    id

    string

    Specifies the ID of a backup repository.

    displayName

    string

    Specifies the display name of a backed-up team.

    organizationId

    string

    Specifies the ID of a backed-up organization.

    _links

    Dictionary of string [key] and Object [value]

    Links to related resources (navigation property).

    Example

    The example below returns a resource representation of the backed-up team with the ID 448c5b66-8dcd-4c75-b636-d3b500bce36f whose data is stored in the backup repository with the ID 946ca1af-6859-4300-bb0d-51d27cc78094.

    Request:

    GET https://abc.tech.local:4443/v5/BackupRepositories/946ca1af-6859-4300-bb0d-51d27cc78094/TeamData/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",

     "organizationId": "abc.onmicrosoft.com:00000000-0000-0000-0000-000000000000:00000000-0000-0000-0000-000000000000",

     "_links": {

       "self": {

         "href": "https://abc.tech.local:4443/v5/backuprepositories/946ca1af-6859-4300-bb0d-51d27cc78094/teamdata/448c5b66-8dcd-4c75-b636-d3b500bce36f"

       },

       "organization": {

         "href": "https://abc.tech.local:4443/v5/backuprepositories/946ca1af-6859-4300-bb0d-51d27cc78094/organizationdata/abc.onmicrosoft.com:00000000-0000-0000-0000-000000000000:00000000-0000-0000-0000-000000000000"

       },

       "backupRepository": {

         "href": "https://abc.tech.local:4443/v5/backuprepositories/946ca1af-6859-4300-bb0d-51d27cc78094"

       }

     }

    }

    I want to report a typo

    There is a misspelling right here:

     

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