> ## 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/clientapps/{clientInfoId}/enable

## URL structure&#x20;

```text theme={null}
https://access-service.xy-company.com/api/v1/clientapps/{clientInfoId}/enable
```

where `{clientInfoId}` is the ID for the client application's configuration information.

## Supported methods and overview&#x20;

* `PUT` - used to enable or disable a registered [client application](/2.16/admin/configuring-client-applications.md), based on its configuration information ID. \

  **Note:** This ID value *is not* the [client ID](/2.16/admin/configuring-client-applications.md#client-id) value.

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

## Detailed description&#x20;

This API endpoint enables or disables a registered client application, using the client application's configuration information ID (i.e. not the [client ID](/2.16/admin/configuring-client-applications.md#client-id) value).

Calling this endpoint on a given client application successively toggles between enabling and disabling this client application.

The configuration information ID of the required client application can be obatined by calling the `GET` method of the [\<access-service>/api/v1/clientapps](/2.16/api/access-service-api-v1-clientapps.md) API endpoint, which retrieves a list of field information for all client applications on the Covata Platform.

## Supported roles&#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)):

* [System administrator](/2.16/admin/administering-users.md#system-administrator-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-clientapps-clientinfoid-enable.md#access-service-api-v1-clientapps-clientinfoid-enable-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.