# List the project's client certificates

Canonical page: https://docs.ovok.com/api/signals/list-the-project-s-client-certificates

`GET /v1/signals/certs`

Lists the client certificates registered for your current project. With `SIGNALS_MTLS_ENABLED` on, every call into Signals through `/v1/signals/api/*` must present one of them.

**Auth:** A client credential cannot read or change them.
**Scope:** the caller's project (from the token).

## Behaviour

- Each certificate is known by `sha256`, its SHA-256 fingerprint in lowercase hex. Ovok never holds a private key.
- A project holds at most two: the one in use and one to rotate to.
- A certificate past `notAfter` stays listed until it is removed, but calls presenting it are refused.
- `environment` says what this Ovok environment can do: `issues` (a CA to issue from a CSR), `registers` (a CA it trusts for registration) and `forwardsCertificates` (an edge that passes client certificates on, which `SIGNALS_MTLS_ENABLED` needs). Check it before offering an action that would answer 501 or 409.
- `environment.caCertificate` is the CA Ovok issues from, PEM, or null where it issues none.
- With `SIGNALS_MTLS_ENABLED` on, Signals presents its own client certificate on every webhook delivery to your https endpoints. The certificate chains to that CA and carries the subject alternative name `urn:ovok:signals:<environment>`.
- To accept only Signals, verify the client certificate against `caCertificate` and pin that name. Your project's own client certificates chain to the same CA, so the CA alone is not enough.
- Keep verifying the `webhook-signature` too. With the setting off, deliveries carry no client certificate.
- A project without a Signals tenant of its own answers 409 `SIGNALS_TENANT_NOT_OWN`.

## Example

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

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