# Remove a client certificate

Canonical page: https://docs.ovok.com/api/signals/remove-a-client-certificate

`DELETE /v1/signals/certs/{sha256}`

Removes one of your current project's client certificates. From then on, calls presenting it are refused.

**Scope:** the caller's project (from the token).

## Behaviour

- `:sha256` is the certificate's fingerprint as `GET /v1/signals/certs` lists it.
- An unknown fingerprint answers 404 `CERTIFICATE_NOT_FOUND`.
- While `SIGNALS_MTLS_ENABLED` is on, the project's last certificate cannot be removed: 409 `LAST_CERTIFICATE_IN_USE`. Every call into Signals would be refused without one. Register another certificate, or turn mutual TLS off, first.
- The answer is 204 with no body.

## Example

```bash
curl -X DELETE 'https://api.sandbox.ovok.com/v1/signals/certs/3f6c0d2a9b8e7f1c4d5a6b7c8d9e0f1a2b3c4d5e6f708192a3b4c5d6e7f80912' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE3NjcyNjg4MDAsImV4cCI6MTc2NzI3MjQwMH0.Ql3B_ztDvctlyZ2z0vp4sl3ExXRQGkzmxdmTAqxNzZk'
```

**Who can call it:** a project admin. See [roles](/access-policies#who-can-call-a-route).