---
title: "Revoke Oauth Connection"
method: POST
path: "/v1/auth/oauth/connections/{connection_id}/revoke"
tags: ["auth-oauth"]
---

# Revoke Oauth Connection

`POST /v1/auth/oauth/connections/{connection_id}/revoke`

## Request

- Base URL: `https://api.usekeel.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.usekeel.io/v1/auth/oauth/connections/{connection_id}/revoke`
- Auth: none declared

Revoke one of the caller's OAuth connections — its whole chain.

``connection_id`` is the ``id`` the list returns (the ``lineage_id``).
A chain the caller does not hold in their current org — someone else's,
another org's, or one that never existed — is the ordinary 404, so the
route cannot be used to learn whether a lineage id exists.

Idempotent for the owner: revoking a chain that is already dead answers
200 with ``revoked: 0`` rather than an error, so a double-click or a
stale list does not surface a failure.

Stops renewal immediately. The client's current access token is a
stateless 1h JWT and lapses on its own within the hour.

## Path parameters

- `connection_id` string, required

## Headers

- `Authorization` string, nullable
- `X-Org-Id` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/usekeel/apis/keel-api.md) · [All operations](https://skmtc.dev/usekeel/apis/keel-api/llms.txt) · [OpenAPI document](https://skmtc.dev/usekeel/apis/keel-api/revisions/3191ca10b0ab?raw)