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 22, 09:30 UTC
docs: tighten initiate() callout wording
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sushmithamallesh committed
Feb 11, 2026 at 15:47 UTC
753008059a2290641e292038150db03f64027e93
1 file changed
+2
-2
docs/content/docs/tools-direct/authenticating-tools.mdx
+2
-2
@@ -164,7 +164,7 @@ For complete white-labeling including OAuth consent screens (removing Composio's
164
165
#### Redirecting users after authentication
166
167
-You can include custom query parameters in your callback URL to carry context through the auth flow, such as identifying which user or session triggered the connection. Composio preserves your parameters and appends its own after authentication completes:
167
+You can include custom query parameters in your callback URL to carry context through the auth flow, such as identifying which user or session triggered the connection. Composio preserves your parameters and appends its own after authentication completes.
168
169
| Parameter | Description |
170
|-----------|-------------|
@@ -249,7 +249,7 @@ console.log(`Connection established: ${connectedAccount.id}`);
249
</Tabs>
250
251
<Callout type="info">
252
-Your callback URL can include query parameters to carry context through the auth flow. Note that `initiate()` uses camelCase parameters (`connectedAccountId`, `appName`) in the redirect, unlike `link()` which uses snake_case (`connected_account_id`). See [Redirecting users after authentication](#redirecting-users-after-authentication) for details.
252
+When using callback URLs with `initiate()`, the appended query parameters use camelCase (`connectedAccountId`, `appName`) instead of snake_case. See [Redirecting users after authentication](#redirecting-users-after-authentication).
253
</Callout>
254
255
#### Services with Additional Parameters