> ## 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.

# <access-service>/api/v1/collaborations/items/{itemId}

## URL structure&#x20;

```text theme={null}
https://access-service.xy-company.com/api/v1/collaborations/items/{itemId}
```

where `{itemId}` is the ID of a Secure Object or collection.

## Supported methods and overview&#x20;

* `DELETE` - used to allow a Covata user to remove themselves as a collaborator from a [Secure Object](/2.16/api/creating-secure-objects-and-collections.md#secure-object) or [collection](/2.16/api/creating-secure-objects-and-collections.md#collection) (i.e. [item](/2.16/api/creating-secure-objects-and-collections.md#item)), based on the item's ID.

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

## Detailed description&#x20;

This API endpoint allows the currently authenticated Covata user<sup>\*</sup> to remove themselves as a collaborator from either a Secure Object or a collection, based on this item's ID.

The item's ID can be obtained by calling the [\<access-service>/api/v1/items](/2.16/api/access-service-api-v1-items.md) API endpoint, which retrieves a list of information associated with Secure Objects and collections that can be filtered using various 'search' criteria.

If the item's ID is that of a collection, then the currently authenticated user is removed from all items contained within this collection.

> [!NOTE]
>
> This functionality is equivalent to a Covata user either removing their access to secure content (shared with them) through the [Safe Share web application](/2.16/user/managing-secure-content.md#removing-your-access-to-secure-content-shared-with-you) as well as Safe Share for [Windows](/2.16/windows.md) or iOS.

<sup>\*</sup> The currently authenticated user is determined by the access token passed in the [header](/2.16/api/access-service-api-v1-collaborations-items-itemid.md#access-service-api-v1-collaborations-items-itemid-required-headers) of requests to this endpoint.

## Supported roles and conditions&#x20;

This API endpoint supports the following Covata user [roles](/2.16/admin/administering-users.md#a-users-roles) (as described in the [Covata Platform Administrator's Guide](/2.16/admin.md)) and conditions:

* [Originator](/2.16/admin/administering-users.md#originator-role) - a Covata user with this role can call this endpoint for an item they are a collaborator on.
* [Collaborator](/2.16/admin/administering-users.md#collaborator-role)

The Covata Platform's resources available to one of these Covata users (above) is determined by the access token passed in the [header](/2.16/api/access-service-api-v1-collaborations-items-itemid.md#access-service-api-v1-collaborations-items-itemid-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.