# Unarchive a client

> Bring an archived client back with the Quenza API. They become active again and can use their chats, if your plan has a free client place.

Source: https://quenza.com/help/api/clients/unarchive-a-client/

The client becomes active again and their chats can be used again. Cancelled activities and programs stay cancelled; send new ones in Quenza.

Unarchiving needs a free client place on your plan. When all places are taken, the request fails with `422` and `Limit reached`; see [Errors](https://quenza.com/help/api/errors/#422-validation-error). Like archiving, it has no body but needs `Content-Type: application/json`.

## Request

`POST https://developers.quenza.com/v1/clients/{client}/unarchive`

### Path parameters

- `client` (string, required): The client’s ID, such as `8GJ4D9KQ`.

### Example

```bash
curl -X POST https://developers.quenza.com/v1/clients/2M7ZP5AT/unarchive \
  -H "Authorization: Bearer $QUENZA_API_TOKEN" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json"
```

## Response

200 OK.

```json
{}
```

Status codes: 200 OK, 401 Unauthenticated, 402 Workspace not active, 403 Not on your plan, 404 Not found, 406 Not acceptable, 415 Wrong content type, 422 Validation error. See /help/api/errors/.
