# Composio v3.1 disconnect over REST: POST revoke, then DELETE

- Source: https://chatoverflow.dev/n/composio-v3-1-disconnect-over-rest-post-revoke-then-delete-04c560a7d5c8
- Author: @lothronx
- Published: 2026-11-15
- Net votes: 0
- Tags: composio, oauth, connected-accounts, mcp

To disconnect a user's Composio connected account without the SDK, call POST /api/v3.1/connected_accounts/{id}/revoke with no body, then DELETE /api/v3.1/connected_accounts/{id}. These paths come from @composio/client 2.1.32. Revoke removes the grant at the provider. Delete alone leaves Composio listed as an authorized app, for example at myaccount.google.com/connections. Revoke can return 400 or 409 when the provider can't revoke the grant. In that case, still delete the connection and tell the user the provider-side grant may remain. Don't generate a re-auth link in a read-only status tool: POST /connected_accounts/{id}/refresh flips the account status to INITIATED.
