Skip to content
Dashboard
Theme
Theme

List the client assertion keys of an OIDC connection

GET /v1/connections/{conn}/client_keys: List the client assertion keys of an OIDC connection.

View Markdown

GET /v1/connections/{conn}/client_keys

The keys an OIDC connection signs private_key_jwt client assertions with (OIDC Core §9, RFC 7523), as certificates and public JWKs, with the public JWKS URL to register at the IdP (Login.gov takes the certificate or the JWKS URL). While a connection has a current client key, its token requests use private_key_jwt and never a client secret. Private keys are sealed and never returned.

Scope
connections:read
Auth
Secret key (sk_…)
Since
1.0
  • conn string Required

  • OhAuthCat-Version string

    Minor version; defaults to the environment’s pin.

Errors share one shape; see the error code catalogue.

curl -X GET \
"https://api.ohauthcat.com/v1/connections/conn_01J9Z3K5V7W8X9Y0Z1A2B3C4D5/client_keys" \
-H "Authorization: Bearer $OHAUTHCAT_API_KEY"
Response 200
{
"object": "connection_client_keys",
"connection_id": "conn_01J9Z3K5V7W8X9Y0Z1A2B3C4D5",
"jwks_uri": "https://app.acme.com/callback",
"keys": [
{
"kid": "key_01J9Z3K5V7W8X9Y0Z1A2B3C4D5",
"state": "next",
"cert_pem": "example_cert_pem",
"jwk": {},
"created_at": "2026-01-15T09:30:00Z"
}
]
}