@devries-cameron20 / composio Mirror · read-only / commits / a4aa8dc22
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, 23:30 UTC

docs(changelog): tighten raw-tokens section

Anshu Garg committed Apr 21, 2026 at 01:43 UTC a4aa8dc22d72740ed2aa0daade6fbb7c3e9ca89e
1 file changed +4 -6
docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
+4 -6
@@ -66,15 +66,13 @@ The same treatment applies to the `data`, `params`, and `headers.Authorization`
66 - [`GET /api/v3/connected_accounts`](https://docs.composio.dev/rest-api/connected-accounts/get-connected-accounts)
67 - [`POST /api/v3/connected_accounts`](https://docs.composio.dev/rest-api/connected-accounts/post-connected-accounts)
68
69 -## If your workflow reads tokens directly
69 +## If you need raw tokens
70
71 -A small number of workflows — typically those that call provider APIs outside of Composio's execution path — read `access_token` or `refresh_token` from the connected-accounts response. If that's you, the recommended path is to connect through an auth config you own. Tokens issued against your OAuth application belong to you, and the connected-accounts API returns them in full (subject to your project's masking setting).
71 +To keep reading `access_token` or `refresh_token` from API responses, connect through your own auth config. Tokens issued against an OAuth application you own are returned in full (subject to your project's masking setting).
72
73 -Getting set up:
74 -
75 -1. Register an OAuth application with the provider — for Gmail, you can start in the [Google Cloud Console](https://console.cloud.google.com/apis/credentials).
73 +1. Register an OAuth application with the provider — for Gmail, start in the [Google Cloud Console](https://console.cloud.google.com/apis/credentials).
74 2. [Create a custom auth config](https://docs.composio.dev/rest-api/auth-configs/post-auth-configs) using those credentials.
77 -3. Create new connections against that auth config. Response fields behave as they always have for customer-owned configs.
75 +3. Create new connections against that auth config.
76
77 <Callout type="info">
78 **No action is needed for most teams.** If you build on the Composio SDK, Tool Router, or MCP, your integrations keep working as-is. If your application reads `access_token` or `refresh_token` directly from a Composio-managed connection, moving those connections onto a custom auth config preserves the previous response shape.