This is an archive version of the document. To get the most up-to-date information, see the current version.

(GET) /BackupRepositories/{repositoryId}/SiteData/{siteId}

In this article

    Returns a resource representation of the backed up Microsoft SharePoint site data having a specified ID which is stored on a Veeam Backup for Microsoft Office 365 repository having a specified ID.

    Request

    To get a resource representation of the backed up Microsoft SharePoint site data with a specified ID which is stored on a Veeam Backup for Microsoft Office 365 repository, send the GET HTTPS request to the URL of the /SiteData/{siteId} resource:

    HTTPS Request

    GET https://<Backup-Office365>:4443/v3/BackupRepositories/{repositoryId}/SiteData/{siteId}

    Request Headers

    The request header must contain the authorization token for the current logon session.

    Request Body

    None.

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

    Response Body

    In the response body, the server returns a representation of the /BackupRepositories/{repositoryId}/SiteData/{siteId} resource.

    Example

    The example below returns an entity representation of the backed up Microsoft SharePoint site data with an ID 4a971c63-7012-4610-8265-9f4775c7d16e8507931c-4561-4ddf-bc90-411aba44bb39.

    Request:

    GET https://support.east.local:4443/v3/BackupRepositories/459684e0-cb24e-4364-8b3c-e3aaeab4fb41/SiteData/4a971c63-7012-4610-8265-9f4775c7d16e8507931c-4561-4ddf-bc90-411aba44bb39

     

     

    Request Header:

    Authorization: Bearer <Access-Token>

     

    Response:

    200 OK

     

    Response Body:

     {

     "id": "4a971c63-7012-4610-8265-9f4775c7d16e8507931c-4561-4ddf-bc90-411aba44bb39",

     "title": "Research",

     "url": "http://research",

     "organizationId": ":00000000-0000-0000-0000-000000000000:f56a5126-37b5-40eb-ba09-7ad7600b9afc",

     "_links": {

       "self": {

         "href": "https://127.0.0.1:4443/v3/backuprepositories/459684e0-ca4e-4164-8c3c-e3aaeab4fb41/sitedata/4a971c63-7012-4610-8265-9f4775c7d16e8507931c-4561-4ddf-bc90-411aba44bb39"

       },

       "organization": {

         "href": "https://127.0.0.1:4443/v3/backuprepositories/459684e0-ca4e-4164-8c3c-e3aaeab4fb41/organizationdata/:00000000-0000-0000-0000-000000000000:f56a5126-37b5-40eb-ba09-7ad7600b9afc"

       },

       "backupRepository": {

         "href": "https://127.0.0.1:4443/v3/backuprepositories/459684e0-ca4e-4164-8c3c-e3aaeab4fb41"

       }

     }

    }

    I want to report a typo

    There is a misspelling right here:

     

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