Create a client secret
Creates a secret for the application, to start using secrets or to rotate them. Requires organization:update. Only this response holds the secret. An application holds at most 5 active secrets (409).
/organizations/{organizationId}/oauth-clients/{clientId}/secretsAuthorizationBearer token (JWT) · headerrequiredAn access token issued by this service (RFC 9068), in the Authorization header as Bearer <token>.
organizationIdstring<uuid>requiredclientIdstring<uuid>requiredThe client's id, the uuid in its cli_<id> client_id.
application/jsonexpires_atstring<date-time>When the secret stops authenticating the client, in the future. Without it the secret does not expire.
The new secret, with its value.
idstring<uuid>requiredsecretstringThe secret, kapten_sk_ followed by 43 base64url characters. Present only in the response that created it; it cannot be read again.
hintstringrequiredThe secret's last four characters, to tell secrets apart.
created_atstring<date-time>requiredexpires_atstring<date-time>When the secret stops authenticating the client; absent when it does not expire.
revoked_atstring<date-time>Set once the secret is revoked; it then authenticates nothing.
The request failed.
errorstringrequiredStable machine-readable code.
invalid_requestunauthorizedforbiddennot_foundconflictgoneunavailableinternalmessagestringrequiredHuman-readable explanation.