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, 00:45 UTC
docs: move bearer token callout inside bearer token section
Dhawal Upadhyay committed
Apr 9, 2026 at 22:07 UTC
9ba5bf1c91457f3950e4c72a75c291b243107cc9
1 file changed
+5
-5
docs/content/docs/importing-existing-connections.mdx
+5
-5
@@ -26,10 +26,6 @@ graph LR
26
2. **The existing credentials** for each user (API keys, bearer tokens, username/password, etc.)
27
3. **A user ID** for each user — any string that uniquely identifies them in your system
28
29
-<Callout type="info">
30
-Bearer token auth configs work with **any toolkit that supports OAuth2 or S2S auth** — including Gmail, GitHub, Slack, Google Docs, and more. This lets you use existing access tokens without setting up an OAuth app.
31
-</Callout>
32
-
29
## API keys
30
31
For services that use API key authentication (e.g., SendGrid, Tavily, PostHog):
@@ -78,7 +74,11 @@ console.log('Connected:', connection.id);
74
75
## Bearer tokens
76
81
-For services where you already have an access token. Bearer token is supported for **all toolkits that have OAuth2 or S2S auth** — including Gmail, GitHub, Slack, Google Docs, and more. It also supports the same additional parameters as the original auth scheme (e.g., `subdomain`, `base_url`).
77
+For services where you already have an access token.
78
+
79
+<Callout type="info">
80
+Bearer token is supported for **all toolkits that have OAuth2 or S2S auth** — including Gmail, GitHub, Slack, Google Docs, and more. This lets you use existing access tokens without setting up an OAuth app. It also supports the same additional parameters as the original auth scheme (e.g., `subdomain`, `base_url`).
81
+</Callout>
82
83
<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
84
<Tab value="Python">