Skip to main content
DELETE
Revoke one person's delegated-OAuth connection
The stored refresh and access tokens are destroyed, not flagged: the table refuses a revoked row that still holds ciphertext. That person’s next tool call on this server is refused until they connect again. This does not revoke KnoxCall’s authorization at the upstream. If you need it gone there too, remove the app in the upstream’s own account settings — only the account holder, or that provider’s admin, can do that. Requires the delete capability on ai_gateway. See the control-plane overview for authentication, the {data, meta} envelope and error types.

Authorizations

Authorization
string
header
required

OAuth 2.1 authentication — recommended for new integrations. Access tokens (kc_ prefix) are minted at the root-host token endpoint https://api.knoxcall.com/oauth/token and passed as Authorization: Bearer <access_token>. Public clients must use PKCE with the authorization_code grant; confidential clients may use client_credentials. The first-party SDKs and the knoxcall login CLI handle token minting, caching, refresh, and DPoP for you.

Path Parameters

id
string<uuid>
required

The MCP server UUID.

grantId
string<uuid>
required

The connection UUID.

Response

The revoked connection id.

data
object
meta
object

Metadata included with every API response.