Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs: Deprecate BEARER_TOKEN auth for 20 toolkits
Co-authored-by: rahul.lingala <rahul.lingala@composio.dev>
Cursor Agent committed
Dec 30, 2025 at 10:06 UTC
3f90766622605c24229631e198b16b1f5100d263
1 file changed
+37
fern/pages/src/changelog/12-30-25-bearer-token-deprecation.md
new
+37
@@ -0,0 +1,37 @@
1
+## Deprecating `BEARER_TOKEN` auth scheme for 20 toolkits
2
+
3
+We’ve **deprecated** the `BEARER_TOKEN` auth scheme for the following **20 toolkits**:
4
+
5
+- `airtable`
6
+- `baserow`
7
+- `discord`
8
+- `discordbot`
9
+- `formsite`
10
+- `gmail`
11
+- `googlecalendar`
12
+- `googledocs`
13
+- `googledrive`
14
+- `googleslides`
15
+- `googlesuper`
16
+- `hubspot`
17
+- `microsoft_clarity`
18
+- `onepage`
19
+- `pipedrive`
20
+- `prisma`
21
+- `sentry`
22
+- `slack`
23
+- `slackbot`
24
+- `trello`
25
+
26
+### Recommendation
27
+
28
+For these toolkits, we recommend using **alternative auth schemes** (for example, `OAUTH2`, `API_KEY`, or other toolkit-supported schemes) instead of `BEARER_TOKEN`.
29
+
30
+### Backward compatibility (explicit)
31
+
32
+This change is **fully backward compatible**:
33
+
34
+- **Existing** auth configs and connected accounts created with `BEARER_TOKEN` **will continue to function**.
35
+- **Creating new** auth configs and connected accounts with `BEARER_TOKEN` **will continue to work** (e.g., via API/SDK).
36
+- To discourage new usage, `BEARER_TOKEN` auth configs / connected accounts **will not be displayed in the UI** for these toolkits.
37
+