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, 23:30 UTC
docs(changelog): drop redundant change-matrix table
Anshu Garg committed
Apr 21, 2026 at 01:44 UTC
99f61eb7714fb88c9d6dc3feb7a87da6019e723e
1 file changed
+2
-11
docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
+2
-11
@@ -21,16 +21,7 @@ You can tell a connection is Composio-managed by the `auth_config.is_composio_ma
21
22
Because the OAuth application is shared across every team on that default, any action a provider takes on it — rate limits, scope adjustments, or in the extreme case, suspending the OAuth client — affects everyone using it. Keeping the credentials inside Composio protects the reliability of the shared integrations, and tool execution continues to work without any change; Composio uses the tokens server-side.
23
24
-## What changes in the API
25
-
26
-| Connection type | Project masking setting | Tokens in response |
27
-|---|---|---|
28
-| Composio-managed | On | Masked (unchanged) |
29
-| Composio-managed | Off | **Masked (new behavior)** |
30
-| Your own auth config | On | Masked (unchanged) |
31
-| Your own auth config | Off | Returned in full (unchanged) |
32
-
33
-### Example
24
+## Example
25
26
Before, with project masking disabled on a Composio-managed Gmail connection:
27
@@ -60,7 +51,7 @@ After:
51
52
The same treatment applies to the `data`, `params`, and `headers.Authorization` fields wherever these values would otherwise appear.
53
63
-### Affected endpoints
54
+## Affected endpoints
55
56
- [`GET /api/v3/connected_accounts/{id}`](https://docs.composio.dev/rest-api/connected-accounts/get-connected-accounts-by-nanoid)
57
- [`GET /api/v3/connected_accounts`](https://docs.composio.dev/rest-api/connected-accounts/get-connected-accounts)