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

## URL structure&#x20;

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

## Supported methods and overview&#x20;

* `GET` - retrieves a list of information about third party (i.e. non-Cocoon Data) client applications which the [Cocoon Data user](/CS1.2/api/authentication-and-authorisation.md) (whose [access token is submitted in the request](/CS1.2/api/access-service-api-v1-users-me-applications-approvals.md#access-service-api-v1-users-me-applications-approvals-supported-roles) to this endpoint) has approved access to their resources on the Cocoon Data Platform.

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

## Detailed description&#x20;

This API endpoint retrieves a list of information about third party (i.e. non-Cocoon Data) client applications which the Cocoon Data user (whose access token is submitted in the request to this endpoint) has approved access to their resources on the Cocoon Data Platform.

This *application approval* process is a step that occurs after the user signs in from a third party client application which utilises the *authorisation code* or *implicit* OAuth 2.0 grant types - i.e. via the [\<access-service>/api/oauth/authorize](/CS1.2/api/access-service-api-oauth-authorize.md) API endpoint.

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

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

## Supported roles&#x20;

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

* [Originator](/CS1.2/admin-org/administering-users-within-an-organisation.md#originator-role)
* [Collaborator](/CS1.2/admin-org/administering-users-within-an-organisation.md#collaborator-role)
* [Ad hoc](/CS1.2/admin-org/administering-users-within-an-organisation.md#adhoc-role)
* [SafeShare administrator](/CS1.2/admin-platform/administering-platform-administrator-users.md#platform-administrator-role)
* [Organisation administrator](/CS1.2/admin-org/administering-users-within-an-organisation.md#organisation-administrator-role)

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

## Required headers&#x20;

The appropriate access token as the `Bearer` token:

* `Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJleHAiOjE0NjcwMTY2NjYsInVzZXJfbmFtZSI6ImFsZXgub...`

## Returns&#x20;

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

For successful requests only, a JSON-formatted response containing the following members is also returned:

* **applications** - An array containing information about all third party client applications which the Cocoon Data user (whose [access token is submitted in the request](/CS1.2/api/access-service-api-v1-users-me-applications-approvals.md#access-service-api-v1-users-me-applications-approvals-supported-roles) to this endpoint) has approved access to their resources on the Cocoon Data Platform. One of this array's elements contains the member **id**, whose value is the application's approval ID, which can be utilised to [revoke the access that this application has to the user's resources](/CS1.2/api/access-service-api-v1-users-me-applications-approvals-approvalid.md).

  **Example (response):**

  ```json theme={null}
  {
      "applications": []
  }
  ```


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