---
title: "Archive Drive Endpoint"
description: "Details about the Drive archive endpoint for Disguise Cloud"
url: https://developer.disguise.one/cloud/management/drive-archive/
---

# Archive Drive

-   [Endpoints](#endpoints)
-   [Response Structure](#response-structure)
-   [Response Example](#response-example)
    -   [Success](#success)
    -   [Errors](#errors)

The `/archive` endpoint of the Disguise Cloud API archives a specific drive by its unique identifier.

When you archive a drive, it is no longer accessible through the API (except for restoring) and is not visible in the Disguise Cloud Drive app  
outside of the archived drives section.

Your drive will be archived and not deleted, so you can restore it at any time, and none of your  
data will be lost. Archived drives do not count towards your organisation’s drive limit.

Please Note

You can not archive your primary drive. If you need to archive your primary drive, please contact \[Disguise Support\](mailto:cloud.support@disguise.one).

## Endpoints

`POST https://api.disguise.cloud/v1/drives/{{uuid}}/archive`

Archive a specific drive by its unique identifier.

## Response Structure

The response from the `/archive` endpoint includes the following fields:

| Field | Type | Description |
| --- | --- | --- |
| **message** | string | If successful, the message will be \`Drive archived’. |

## Response Example

```bash
curl -X POST https://api.disguise.cloud/v1/drives/{{uuid}}/archive \
-H "Authorization: Token YOUR_API_TOKEN"
```

### Success

A successful response will return a `200 OK` status code and the following JSON:

```json
{
  "message": "Drive archived"
}
```

### Errors

If the drive cannot be found or is already archived, the response will return a `404 Not Found` status code and the following JSON:

```json
{
  "error": {
    "message": "Drive not found",
    "details": "The drive you are trying to archive either does not exist or has already been archived"
  }
}
```
