Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
TypeScript agentic-aiagentsaiai-agentsaiagentsdeveloper-toolsfunction-callinggpt-4javascriptjsllmllmopsmcppythonremote-mcp-serverssetypescript
docs(changelog): delete 'If you need raw values' section; inline the migration guidance
Anshu Garg1f8ab767401c
diff --git a/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx b/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdxindex f5d8e25fc..b3a7c386d 100644--- a/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx+++ b/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx@@ -64,6 +64,8 @@ After:Connections on customer-owned auth configs are unaffected — token visibility follows your existing `mask_secret_keys_in_connected_account` setting (`xxxx...` truncation when enabled, raw passthrough when disabled).+If you were reading Composio-managed access or refresh tokens from these responses — typically because you use Composio for OAuth and then call the provider's APIs yourself — register your own OAuth application with the provider and [create a custom auth config](/reference/api-reference/auth-configs/postAuthConfigs) against those credentials. Tokens issued against an OAuth application you own belong to you and are returned in full (subject to `mask_secret_keys_in_connected_account`).+### 2. Auth-config credentials`GET /api/v3/auth_configs` and `GET /api/v3/auth_configs/{id}` no longer return sensitive credentials in a recoverable form.@@ -93,16 +95,6 @@ Auth configs:- [`GET /api/v3/auth_configs/{id}`](/reference/api-reference/auth-configs/getAuthConfigsByNanoid)- [`GET /api/v3/auth_configs`](/reference/api-reference/auth-configs/getAuthConfigs)-### If you need raw values--**Connected-account tokens.** Connect through a customer-owned auth config, and optionally set `mask_secret_keys_in_connected_account: false` on your project.--1. Register an OAuth application with the provider — for Gmail, start in the [Google Cloud Console](https://console.cloud.google.com/apis/credentials).-2. [Create a custom auth config](/reference/api-reference/auth-configs/postAuthConfigs) using those credentials.-3. Create new connections against that auth config.--**Auth-config secrets** (`client_secret`, `developer_token`, etc.). Keep these alongside the code that created the auth config — for example, in your own secret manager at upload time. The auth-config GET endpoints will only return masked or redacted values going forward.-<Callout type="info">If your integration relies on reading `access_token`, `refresh_token`, `client_secret`, or `developer_token` from Composio API responses, you will need to act. All other integrations continue to work as before.</Callout>