# Disable a user profile


**POST /_security/profile/{uid}/_disable**

**All methods and paths for this operation:**

<div>
                      <span class="operation-verb put">PUT</span>
                      <span class="operation-path">/_security/profile/{uid}/_disable</span>
                      </div>
                    <div>
                      <span class="operation-verb post">POST</span>
                      <span class="operation-path">/_security/profile/{uid}/_disable</span>
                      </div>
                    

Disable user profiles so that they are not visible in user profile searches.

NOTE: The user profile feature is designed only for use by Kibana and Elastic's Observability, Enterprise Search, and Elastic Security solutions.
Individual users and external applications should not call this API directly.
Elastic reserves the right to change or remove this feature in future releases without prior notice.

When you activate a user profile, its automatically enabled and visible in user profile searches. You can use the disable user profile API to disable a user profile so it’s not visible in these searches.
To re-enable a disabled user profile, use the enable user profile API .

## Required authorization

* Cluster privileges: `manage_user_profile`



## Servers
- http://api.example.com: http://api.example.com ()


## Authentication methods
- Api key auth
- Basic auth
- Bearer auth


## Parameters

### Path parameters
- **uid** (string)
  Unique identifier for the user profile.

### Query parameters
- **refresh** (string)
  If 'true', Elasticsearch refreshes the affected shards to make this operation visible to search.
  If 'wait_for', it waits for a refresh to make this operation visible to search.
  If 'false', it does nothing with refreshes.


## Responses
### 200


#### Body: application/json (object)
- **acknowledged** (boolean)
  For a successful response, this value is always true. On failure, an exception is returned instead.


[Powered by Bump.sh](https://bump.sh)