---
title: "Get restore by restoreID"
method: GET
path: "/endpoints/v1/restores/{restoreID}"
tags: ["Endpoints"]
---

# Get restore by restoreID

`GET /endpoints/v1/restores/{restoreID}`

## Request

- Base URL: `https://apis.druva.com/insync`
- URL: `https://apis.druva.com/insync/endpoints/v1/restores/{restoreID}`
- Auth: API key in header `Authorization`

Returns the restore activity details based on the restore ID.

## Path parameters

- `restoreID` integer, required

## Response `200`

OK

- Restore
  - `deviceID` integer: The unique ID of the device from which the restore activity was triggered. Example: 12345
  - `targetDeviceID` integer: The device ID of the device to which the data was restored. Example: 12345
  - `restoreLocation` string: The location on the device to which the data was restored. The possibles locations are: 1) Original: If the data was restored to the original location 2) Desktop: If the data was restored to desktop 3)Custom location: If data was restored to a custom location 4) Unknown: If the restore was performed to unknown location.
  - `userID` integer: The unique ID of the user who triggered the restore activity. Example: 12345
  - `restoreID` integer: The unique ID of the restore activity. Example: 12345
  - `startTime` string, date-time: The start time of the restore activity. Example: 2013-04-17T09:12:36Z
  - `endTime` string, date-time: The end time of the restore activity. Example: 2013-04-17T09:13:36Z. This value is empty if the restore activity is ongoing.
  - `status` string: Status of the restore activity. It is: 1) Successful: If the restore activity was completed successfully. 2) Ongoing: If the restore activity is ongoing. 3) Failed: If the restore activity was failed. 4) Cancelled: If the restore activity was cancelled manually. 5) Completed with Errors: If some files were missed during the restore activity.
  - `restoreSize` string: The size of the data restored. Example: 285 MB This value is 'Unknown' for restores that failed to start.
  - `numberOfFilesRestored` integer: The total number of files that were restored in the restore activity. Example: 456
  - `numberOfFilesMissed` integer: The total number of files that were missed from the restore activity. Example: 12 This value is 'null' if the restore activity is ongoing.
  - `restoreMode` string: The persona who initiated the restore. Personas are: Self: inSync user himself Admin: Administrator.
  - `systemSettingsRestore` boolean: This returns 'true' if system setting were restored else returns 'false'.
  - `failureReason` string: This returns the failure reason if the status is 'failed' else returns 'empty.

## Other responses

- `400`: Bad Request
- `401`: The request did not include an authentication token or an expired authentication token was supplied.
- `403`: Access denied: Insufficient permissions. User requires specific access rights and minimum permissions. Details: https://help.druva.com/en/articles/15069296
- `404`: The requested resource was not found.
- `500`: The request was not processed due to an internal error in inSync Cloud.
- `501`: Requested HTTP method is not implemented.

---

[API](https://skmtc.dev/druva/apis/insync-cloud.md) - [All operations](https://skmtc.dev/druva/apis/insync-cloud/llms.txt) - [OpenAPI document](https://skmtc.dev/druva/apis/insync-cloud/revisions/a0ce6d05033c?raw)