New Endpoint: Revoke OAuth 2.0 Tokens for a Connected Account
You can now programmatically revoke a connected account’s OAuth 2.0 tokens at the upstream provider, giving you explicit control over when credentials are killed at the third-party — instead of relying on deletion or natural token expiry.The Endpoint
REVOKED and the response reports which token subjects were killed at the provider on this call.
Example request:
200 OK):
revoked_tokens array lists the subjects revoked at the provider during this call. An empty array means the connection was already in a revoked state and no upstream dispatch was issued.
Status Codes
Revoke Is Not Automatic on Delete
Deleting a connected account or a project does not revoke tokens at the upstream provider — the credentials are removed from Composio but may remain live at the third-party until they expire naturally. If you need credentials killed at the provider, follow revoke-then-delete semantics: callPOST /revoke first, then issue the delete.
Revoke Is Best-Effort
Some providers do not expose a programmatic way to revoke one or both token subjects (for example, an access token but no refresh-token revoke route, or no revoke endpoint at all). In those cases, Composio revokes whatever the provider supports and therevoked_tokens array reflects exactly what was killed. Always read revoked_tokens to confirm which subjects were affected — do not assume both access_token and refresh_token were revoked on every call.