@devries-cameron20 / composio Mirror · read-only / commits / 357fa4a9d
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 21:00 UTC

docs(changelog): address review feedback on revoke entry

- Reword 400 row: "Revoke is not supported for this toolkit" - Simplify 404 row to "Connected account does not exist" - Drop "Database failure" wording from 500 row - Drop "(Today)" qualifier and the future-cascade speculation paragraph - Drop the auto-EXPIRED platform-detection claim (not true for non-OAuth2 or OAuth2 without refresh tokens) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> Co-authored-by: sarthak <sarthak@composio.dev>

Zen Agent committed May 12, 2026 at 11:47 UTC 357fa4a9d9d764a259fe5bd4443a66313d01720d
1 file changed +6 -8
docs/content/changelog/05-12-26-connected-accounts-revoke.mdx
+6 -8
@@ -40,16 +40,14 @@ The `revoked_tokens` array lists the subjects revoked at the provider during thi
40 | Code | Meaning |
41 |------|---------|
42 | `200` | Connection revoked (or already revoked — see `revoked_tokens`) |
43 -| `400` | Toolkit is not OAuth 2.0 or has no revoke configuration |
44 -| `404` | Connected account does not exist or its parent auth config was removed |
43 +| `400` | Revoke is not supported for this toolkit |
44 +| `404` | Connected account does not exist |
45 | `409` | Connection is not in a revokable state (only `ACTIVE` and already-`REVOKED` are accepted) |
46 -| `500` | Database failure or every upstream revoke dispatch failed |
46 +| `500` | Server error — revocation could not be completed |
47
48 -### Revoke Is Not Automatic on Delete (Today)
48 +### Revoke Is Not Automatic on Delete
49
50 -Deleting a connected account or a project does **not** currently 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: call `POST /revoke` first, then issue the delete.
51 -
52 -In a future release, we may extend delete to cascade into revoke automatically. We'll announce this separately before changing the behavior; until then, treat the two steps as independent.
50 +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: call `POST /revoke` first, then issue the delete.
51
52 ### Revoke Is Best-Effort
53
@@ -57,4 +55,4 @@ Some providers do not expose a programmatic way to revoke one or both token subj
55
56 ### Externally Revoked Tokens
57
60 -If a user revokes the connection directly with the provider (for example, removing the app from their account on the provider's website), the upstream revoke call from this endpoint may return an error. Such connections are eventually detected and marked as `EXPIRED` by the platform — you do not need to take additional action, but you should expect the revoke call itself to fail in that window.
58 +If a user revokes the connection directly with the provider (for example, removing the app from their account on the provider's website), the upstream revoke call from this endpoint may return an error. Handle this case by treating the connection as already revoked on your side.