---
title: "Preserve a user"
method: POST
path: "/usermanagement/v1/users/{userID}/preserve"
tags: ["User Management"]
---

# Preserve a user

`POST /usermanagement/v1/users/{userID}/preserve`

## Request

- Base URL: `https://apis.druva.com/insync`
- URL: `https://apis.druva.com/insync/usermanagement/v1/users/{userID}/preserve`
- Auth: API key in header `Authorization`

Preserves a user in Druva inSync.
When you preserve a user:
    1) Backups from the user's device are stopped and the user status changes to Preserved.
    2) inSync retains the user's data backups as long as the user is Preserved.
    3) If not activated again, the preserved user is later deleted from inSync after the duration specified in the  Auto-Delete Preserved User settings of the user's profile.

## Path parameters

- `userID` integer, required

## Response `200`

OK

- unknown

## 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.
- `422`: The request was well-formed but was not processed due to semantic errors.
- `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)