This is an archive version of the document. To get the most up-to-date information, see the current version.Get Discovered Computer
You can get a resource representation of a discovered computer with the specified UID.
Required Privileges
To perform this task, a user must have one of the following roles assigned: Portal Administrator, Service Provider Global Administrator, Service Provider Administrator, Company Owner, Company Administrator.
Request
To get a representation of a discovered computer, send the GET HTTP request to the URL of the /discovery/computers/{computerUid} resource.
HTTP Request
GET https://<hostname>:1280/api/v3/discovery/computers/{computerUid} |
Request Headers
The request contains the following headers.
Header | Required/Optional | Value | Description |
Authorization | Required | Bearer <Access-Token> | Authenticates a client who sends the request to the server. Must contain the access token for the current logon session in the Bearer <Access-Token> format. |
Accept | Optional | application/json | Specifies a media type of representation that is required in the response message. If the requested type is not supported, the server will return the response in the application/json media type. |
Request parameters
A list of parameters that are applicable for this operation:
Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
computerUid | Path | String (uuid) | Yes | — | Computer UID |
Response
The server returns the following response to the client.
Response Code
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 HTTP 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, Veeam Service Provider Console returns a resource representation based on the DiscoveredComputer schema.
Example 
The following request returns a representation of a discovered computer with UID 18d1b24d-0a32-4072-9ccc-1fab5176fd7a.
Request: GET https://localhost:1280/api/v3/discovery/computer/18d1b24d-0a32-4072-9ccc-1fab5176fd7a
Request Header: Authorization: Bearer <Access-Token>
Response Code: 200 OK
Response Body: { "data": { "instanceUid": "18d1b24d-0a32-4072-9ccc-1fab5176fd7a", "ruleUid": "b1735ae2-2368-4438-958c-e39507bb6710", "managementAgentUid": "96405a83-d838-4a9d-ada9-80fca4a667a8", "discoveredTime": "2020-03-08T04:19:01.6144435+03:00", "backupAgentInstallationStatus": "Installed", "backupAgentVersion": "4.0.0.1811", "backupAgentManagementStatus": "ManagedByConsole", "info": { "uniqueUid": "d4aa60ab-db8e-4012-a450-8a8ad6205fc1", "biosUuid": "e77a8297-5e28-48d1-9c26-2a82ae8ecf23", "hostName": "srv03", "fqdn": "srv03.prod.local", "guestOs": "Microsoft Windows Server 2016 Standard", "guestOsType": "server", "guestOsVersion": "10.0.14393", "guestOsSku": 7, "platformType": "vSphere", "ipAddresses": [ "172.24.145.33" ], "macAddresses": [ "00:50:56:BB:1C:E8" ] } } } |