# Archive a client

> Archive a client through the Quenza API when you stop working with them. Assignments are cancelled and their chats become read-only.

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

Archiving keeps the client's history in Quenza but ends your work together:

- Activities and programs that are still running are cancelled.
- Their chats become read-only.
- Their `status` becomes `archived` and `archived_at` is set.

The request has no body, but it still needs `Content-Type: application/json`. To undo it, [unarchive the client](https://quenza.com/help/api/clients/unarchive-a-client/). [Archive clients](https://quenza.com/help/clients/archive-clients/) explains the same in the app.

## Request

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

### Path parameters

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

### Example

```bash
curl -X POST https://developers.quenza.com/v1/clients/2M7ZP5AT/archive \
  -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. See /help/api/errors/.
