Revoke OAuth config

Revokes a server-level OAuth configuration and its associated access token. After revocation, the MCP client will no longer be able to use this OAuth token. Revocation is not terminal for the client: an admin can restore access by redoing consent via POST /api/mcp/client//reauthorize, which runs against the credentials currently stored on the client’s OAuth config.

DELETE /api/oauth/config/{id}

Error

A valid request URL is required to generate request examples

200

{
  "status": "success",
  "message": "Operation completed successfully"
}

Authorizations

ManagementBearerAuthBasicAuth

Authorization · string · header · required

Management API authentication for /api/* endpoints. Use the Authorization header with Bearer <token>, where <token> is one of:

• a Bifrost management API key,
• a dashboard session token issued by POST /api/session/login,
• base64 of <admin-username>:<admin-password> (legacy equivalent of BasicAuth).

Virtual keys (sk-bf-*) and the x-api-key header are not accepted on management APIs - the sole exception is GET /api/governance/virtual-keys/quota, which is virtual-key-only.

Path Parameters

id · string · required

OAuth config ID

Response

200

application/json

OAuth token revoked successfully

Generic success response

status · string

Example:

"success"

message · string

Example:

"Operation completed successfully"