Regenerate client secret
Changed onGenerates a fresh client secret for an OAuth app. The previous secret is invalidated immediately — any client still presenting it will fail token exchange at POST /oauth2/token until updated.
The new secret is returned in this response only and cannot be retrieved later. Pair this call with credential propagation to every integration that uses the app. If the rotation was triggered by a suspected leak, also call POST /oauth-clients/{appId}/revoke-all-tokens to invalidate already-issued access and refresh tokens instead of waiting for their natural expiry.
Creator-only: even org admins cannot rotate secrets for other users' apps.
Request
- Base URLhttps://app.pipeshub.com/api/v1
- URLhttps://app.pipeshub.com/api/v1/oauth-clients/{appId}/regenerate-secret
- AuthHTTP bearer
Path parameters
OAuth app ID
Response
New client secret generated
Example response
{
"message": "Client secret regenerated successfully"
}Changes
- info
added the non-success response with the status
- info
added the non-success response with the status
- info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status
- info