---
title: "List mTLS certificate authorities"
canonical: "https://bird.com/docs/api/reference/list-workspace-mtls-certificate-authorities"
---

# List mTLS certificate authorities

`GET /v1/workspace/mtls-certificate-authorities`

Returns the certificate authorities that issue the client certificates of your workspace. A workspace has at most two.

## Servers

- `https://{region}.platform.bird.com`: Regional API endpoint. Use the host for the region your organization is hosted in. Official Bird SDKs and the CLI select it automatically from your API key, so you rarely need to set it by hand.
  - `region`: `us1`, `eu1`. Default: `us1`. The region your organization's data is hosted in.
- `https://platform.bird.com`: Region-independent endpoint for authentication and account administration.
- `http://localhost:8080`: Local development.

## Authentication

Use one authentication option:

- `BearerAuth`: HTTP bearer authentication. Pass the API key as a bearer token in the `Authorization` header. Workspace
keys use `bk_{region}_*`; organization master keys use `bm_{region}_*`.
The prefix identifies the region and selects the
API endpoint. Official Bird SDKs and the CLI derive the region from the key.

- `CookieAuth`: Send `bird_session` in cookie. Session cookie set after signing in to the Bird dashboard. The cookie
value is an opaque session token; no session data is stored in the cookie
itself.

## Code samples

**cURL**

```sh
curl -X GET "https://us1.platform.bird.com/v1/workspace/mtls-certificate-authorities" \
  -H "Authorization: Bearer $TOKEN"
```

Examples: [cURL](/docs/api/reference/list-workspace-mtls-certificate-authorities.curl.md)

## Example response `200`

```json
{
  "data": [
    {
      "id": "mtlsca_01krdgeqcxet5s7t44vh8rt9mg",
      "subject": "CN=Example Client CA,O=Example Inc.",
      "fingerprint_sha256": "9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08"
    }
  ]
}
```

## Header parameters

- `X-Workspace-Id` (string, optional): Workspace context for the request. Required for dashboard authentication and master keys. Workspace keys and access tokens already identify their workspace; send that workspace or omit the header. A different one is rejected.
- `X-Organization-Id` (string, optional): Organization context for the request. Required for dashboard authentication. An API key or access token carries its own organization, so send either that organization or no header at all; a different one is rejected.

## Response body

- `data` (array of object, required)
- `data.id` (string, required)
- `data.subject` (string, required): The distinguished name of the certificate authority.
- `data.fingerprint_sha256` (string, required): The SHA-256 fingerprint of the certificate, in lowercase hexadecimal.
- `data.not_before` (string, required): Start of the validity period of the certificate authority.
- `data.not_after` (string, required): End of the validity period of the certificate authority.
- `data.created_at` (string, required): When you added the certificate authority.

## Related resources

- [Should I use a Bird SDK or call the API directly?](/explained/platform/should-i-use-an-sdk-or-call-the-api-directly) (answer)
- [Build your first integration](/learn/paths/integration) (course)
- [Send your first email](/docs/get-started/send-your-first-email) (docs)

[Get an implementation brief](/learn/workspace?topic=api-basics)