> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cocoondata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# <content-service>/api/v1/collections/{collectionId}/contents

## URL structure&#x20;

```text theme={null}
https://content-service.xy-company.com/api/v1/collections/{collectionId}/contents
```

where `{collectionId}` is the ID of a collection.

## Supported methods and overview&#x20;

* `DELETE` - used to explicitly delete the encrypted data (associated with all [Secure Objects](/3.2/api/creating-files-and-folders.md#secure-object) contained within a [collection](/3.2/api/creating-files-and-folders.md#collection)) from storage managed by the Covata Platform's Content Service.

> [!NOTE]
>
> This method takes no parameters.

## Detailed description&#x20;

This API endpoint deletes the encrypted data (associated with all Secure Objects contained within a collection) from storage managed by the Covata Platform's Content Service.

The collection is specified by the `{collectionId}` value in the URL.

> [!NOTE]
>
> If you intend to [delete a collection](/3.2/api/access-service-api-v1-collections-collectionid.md) and change the state of all Secure Objects contained within the collection to *Deleted*, then call this API endpoint on this collection *first*. This avoids problems where a Covata user's actual quota differs from the quota reported by the Covata Platform (until this data is automatically deleted by the Content Service). See [\<access-service>/api/v1/collections/\{collectionId}](/3.2/api/access-service-api-v1-collections-collectionid.md) for more information.

## Supported roles and conditions&#x20;

This API endpoint supports the following Covata user roles (as described in the [Covata Platform Administrator's Guide](/3.2/admin.md)), conditions and [permissions](/3.2/api/access-service-api-v1-permissions-sets.md) (where applicable):

* [Originator](/3.2/admin-org/administering-users-within-an-organisation.md#originator-role) - a Covata user with this role can call this endpoint on a collection they own.
* **Originator**, [Collaborator](/3.2/admin-org/administering-users-within-an-organisation.md#collaborator-role) and [Ad hoc](/3.2/admin-org/administering-users-within-an-organisation.md#adhoc-role) - a Covata user with any of these roles can call this endpoint for a collection they are a collaborator on (with the **Remove (Folder)** *permission*).

The Covata Platform's resources available to one of these Covata users (above) is determined by the access token passed in the [header](/3.2/api/content-service-api-v1-collections-collectionid-contents.md#content-service-api-v1-collections-collectionid-contents-required-headers) of requests to this endpoint.

## Required headers&#x20;

The appropriate access token as the `Bearer` token:

* `Authorization: Bearer a1b2c3d4-e5f6-g7h8-i9j0-k1l2m3n4o5p6`

## Returns&#x20;

If the request succeeded, then an HTTP response status `200 OK` is returned.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.