Revoke a per-user-headers credential

Hard-deletes a per-user-headers credential row by primary key. Authorization scoping is enforced server-side — callers may only delete credentials visible to their identity.

The unified DELETE /api/mcp/sessions/ is the more convenient entry point; this typed endpoint exists for callers that already know they’re acting on a header credential row.

DELETE /api/mcp/per-user-headers/credential/{id}

Error

A valid request URL is required to generate request examples

401

{
  "event_id": "<string>",
  "type": "<string>",
  "is_bifrost_error": true,
  "status_code": 123,
  "error": {
    "type": "<string>",
    "code": "<string>",
    "message": "<string>",
    "param": "<string>",
    "event_id": "<string>"
  },
  "extra_fields": {
    "model_requested": "<string>",
    "request_type": "<string>"
  }
}

Authorizations

Authorization · string · header · required

Management API authentication for /api/* endpoints. Use the Authorization header with Bearer <API key>. Virtual keys, dashboard/user/session tokens, and x-api-key headers are not supported on management APIs.

Path Parameters

id · string · required

Credential row primary key

Response

204

Revoked