> ## 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/users/me/applications/approvals/{approvalId}

## URL structure&#x20;

```text theme={null}
https://access-service.xy-company.com/api/v1/users/me/applications/approvals/{approvalId}
```

where `{approvalId}` is an application's approval ID.

## Supported methods and overview&#x20;

* `DELETE` - revokes the access that a third party (i.e. non-Covata) client application (specified by `approvalId`) has to resources on the Covata Platform, which are accessible to a Covata user (whose [access token is submitted in the request](/3.5/api/access-service-api-v1-users-me-applications-approvals-approvalid.md#access-service-api-v1-users-me-applications-approvals-approvalid-supported-roles-and-conditions) to this endpoint).

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

## Detailed description&#x20;

This API endpoint revokes the access that a third party (i.e. non-Covata) client application (specified by `approvalId`) has to resources on the Covata Platform, which are accessible to a Covata user (whose access token is submitted in the request to this endpoint).

An application's approval ID is obtained using the [\<access-service>/api/v1/users/me/applications/approvals](/3.5/api/access-service-api-v1-users-me-applications-approvals.md) API endpoint, which retrieves a list of information about all client applications that this user (whose access token is submitted in the request to this endpoint) has approved access to their resources on the Covata Platform.

Such a client application could be one that you or your organisation is developing, where this application integrates with Covata technologies either using the Covata API.

> [!NOTE]
>
> Before any client application can be granted access to a Covata user's resources, a SafeShare administrator must first have [registered the client application](/3.5/api/access-service-api-v1-clientapps.md) on their Covata Platform instance.

## Supported roles and conditions&#x20;

This API endpoint supports requests utilising Covata user accounts with the following roles (as described in the [SafeShare Administrator's](/3.5/admin-platform/administering-platform-administrator-users.md#platform-administrators-and-user-roles) and [Organisation Administrator's](/3.5/admin-org/administering-users-within-an-organisation.md#an-organisation-users-roles) Guides):

* [Originator](/3.5/admin-org/administering-users-within-an-organisation.md#originator-role), [Collaborator](/3.5/admin-org/administering-users-within-an-organisation.md#collaborator-role), [Ad hoc](/3.5/admin-org/administering-users-within-an-organisation.md#adhoc-role), [SafeShare administrator](/3.5/admin-platform/administering-platform-administrator-users.md#platform-administrator-role) and [Organisation administrator](/3.5/admin-org/administering-users-within-an-organisation.md#organisation-administrator-role) - when this user has approved the client application (specified by `{approvalId}` in the request's URL) access to their resources on the Covata Platform.

The Covata Platform's resources available to one of these Covata users (above) is determined by the access token submitted in the [header](/3.5/api/access-service-api-v1-users-me-applications-approvals-approvalid.md#access-service-api-v1-users-me-applications-approvals-approvalid-required-headers) of requests to this endpoint.

## Required headers&#x20;

The appropriate access token as the `Bearer` token:

* `Authorisation: Bearer eyJhbGciOiJSUzI1NiJ9.eyJleHAiOjE0NjcwMTY2NjYsInVzZXJfbmFtZSI6ImFsZXgub...`

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