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: remove auth config section, fix prereq link, update changelog PATCH description
Dhawal Upadhyay committed
Apr 9, 2026 at 22:02 UTC
b840d4410a920305f8ce744bf6a63443f6d543bb
2 files changed
+3
-72
docs/content/changelog/04-07-26-bearer-token-patch.mdx
+1
-2
@@ -35,7 +35,6 @@ await composio.connectedAccounts.update('ca_abc123', {
35
});
36
```
37
38
-- **Credential rotation** — update expired tokens in place
39
-- **Alias management** — name connections for multi-account scenarios
38
+- **Keep access tokens updated** — call PATCH whenever you refresh the token on your end (e.g., after an OAuth refresh flow)
39
- **Partial updates** — omitted fields are preserved, fields set to `null` are removed
40
- **Supported schemes** — BEARER_TOKEN, API_KEY, BASIC, BASIC_WITH_JWT, GOOGLE_SERVICE_ACCOUNT, SERVICE_ACCOUNT
docs/content/docs/importing-existing-connections.mdx
+2
-70
@@ -22,80 +22,12 @@ graph LR
22
23
## Prerequisites
24
25
-1. **A Composio API key** — from your project settings
25
+1. **An [auth config](/docs/auth-configuration/programmatic-auth-configs)** for the toolkit you're importing into
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
-## Creating an auth config
30
-
31
-Before importing credentials, you need an auth config for the toolkit. This tells Composio which auth scheme to use. This is a one-time setup per toolkit.
32
-
33
-<Tabs groupId="language" items={['Python', 'TypeScript', 'curl']} persist>
34
-<Tab value="Python">
35
-```python
36
-from composio import Composio
37
-
38
-composio = Composio(api_key="your-api-key")
39
-
40
-# For API key toolkits (e.g., SendGrid, Tavily)
41
-auth_config = composio.auth_configs.create("sendgrid", {
42
- "type": "use_custom_auth",
43
- "authScheme": "API_KEY",
44
- "credentials": {},
45
-})
46
-
47
-# For bearer token — works with any OAuth toolkit (Gmail, GitHub, Slack, etc.)
48
-auth_config = composio.auth_configs.create("gmail", {
49
- "type": "use_custom_auth",
50
- "authScheme": "BEARER_TOKEN",
51
- "credentials": {},
52
-})
53
-
54
-print(f"Auth config ID: {auth_config.id}")
55
-```
56
-</Tab>
57
-<Tab value="TypeScript">
58
-```typescript
59
-import { Composio } from '@composio/core';
60
-
61
-const composio = new Composio({ apiKey: 'your-api-key' });
62
-
63
-// For API key toolkits (e.g., SendGrid, Tavily)
64
-const authConfig = await composio.authConfigs.create('sendgrid', {
65
- type: 'use_custom_auth',
66
- authScheme: 'API_KEY',
67
- credentials: {},
68
-});
69
-
70
-// For bearer token — works with any OAuth toolkit (Gmail, GitHub, Slack, etc.)
71
-const authConfig = await composio.authConfigs.create('gmail', {
72
- type: 'use_custom_auth',
73
- authScheme: 'BEARER_TOKEN',
74
- credentials: {},
75
-});
76
-
77
-console.log('Auth config ID:', authConfig.id);
78
-```
79
-</Tab>
80
-<Tab value="curl">
81
-```bash
82
-curl -X POST https://backend.composio.dev/api/v3/auth_configs \
83
- -H 'x-api-key: YOUR_API_KEY' \
84
- -H 'Content-Type: application/json' \
85
- -d '{
86
- "toolkit": {"slug": "gmail"},
87
- "auth_config": {
88
- "type": "use_custom_auth",
89
- "authScheme": "BEARER_TOKEN",
90
- "credentials": {}
91
- }
92
- }'
93
-```
94
-</Tab>
95
-</Tabs>
96
-
29
<Callout type="info">
98
-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 import your own access tokens without setting up an OAuth app.
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
33
## API keys