Skip to content
Dashboard
Theme
Theme

Create or stage a client assertion key

POST /v1/connections/{conn}/client_keys: Create or stage a client assertion key.

View Markdown

POST /v1/connections/{conn}/client_keys

The first call creates the current key (a Login.gov connection gets one on create). Later calls stage a next key, published in the JWKS but not used, so it can be registered at the IdP before activate; a second staged key answers connection_state_conflict. Only OIDC connections have client keys.

Scope
connections:write
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 POST \
"https://api.ohauthcat.com/v1/connections/conn_01J9Z3K5V7W8X9Y0Z1A2B3C4D5/client_keys" \
-H "Authorization: Bearer $OHAUTHCAT_API_KEY"
Response 201
{
"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"
}
]
}