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(fumadocs): sync missing changelogs from fern
Add 7 changelog entries that were added to fern after initial migration: - 12-30-25-proxy-binary-data: Binary Data Support for Proxy Execute - 12-30-25: Webhook Payload V3 announcement - 12-31-25: Deprecating BEARER_TOKEN auth scheme - 01-07-26: Consistent Error Response & Union Types - 01-08-26-mcp-api-key-enforcement: Optional API Key for MCP - 01-09-26: Tool Enum Name Shortening - 01-12-26-tool-router-improvements: Tool Router improvements Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sushmithamallesh committed
Jan 12, 2026 at 15:37 UTC
c3ca84a0f9fb1805e55e5e28adb58dd78bd0f0a4
7 files changed
+840
fumadocs/content/changelog/01-07-26.mdx
new
+179
@@ -0,0 +1,179 @@
1
+---
2
+title: "Consistent Error Response Structure & Union Types Preserved"
3
+date: "2026-01-07"
4
+---
5
+
6
+## Consistent Error Response Structure
7
+
8
+Tool execution errors now return a standardized response format across all failure types. Previously, the `data` field was empty on errors—now it always includes `status_code` and `message`, matching the structure of successful responses.
9
+
10
+### What Changed
11
+
12
+All error responses from tool execution now include:
13
+- `data.status_code`: HTTP status code (or `null` for non-HTTP errors)
14
+- `data.message`: Detailed error message
15
+- `error`: Same detailed message at the top level
16
+
17
+### Before vs After
18
+
19
+**Previous error response:**
20
+```json
21
+{
22
+ "data": {},
23
+ "successfull": false,
24
+ "error": "404 Client Error: Not Found for url: ...",
25
+}
26
+```
27
+
28
+**New error response:**
29
+```json
30
+{
31
+ "data": {
32
+ "http_error": "404 Client Error: Not Found for url: ...",
33
+ "status_code": 404,
34
+ "message": "Resource not found: The requested item does not exist"
35
+ },
36
+ "successfull": false,
37
+ "error": "Resource not found: The requested item does not exist",
38
+}
39
+```
40
+
41
+### Why This Matters
42
+
43
+- **Easier parsing**: Agents and code can reliably access error details from `data.message` without special-casing empty `data` objects
44
+- **Better debugging**: Detailed error messages replace generic HTTP error strings
45
+- **Consistent schema**: Same response shape whether the tool succeeds or fails
46
+
47
+---
48
+
49
+## Union Types Preserved in Tool Schemas
50
+
51
+Tool schemas now use standard JSON Schema `anyOf` for union types, providing accurate type information for LLMs and code generators.
52
+
53
+### What Changed
54
+
55
+Two changes affect how types appear in request/response schemas:
56
+
57
+| Change | Scope | Description |
58
+|--------|-------|-------------|
59
+| **Nullable fields** | **All toolkits** | Fields that accept `null` now use `anyOf: [{type}, {type: "null"}]` instead of `type` + `nullable: true` |
60
+| **Multi-type fields** | 157 toolkits | Fields accepting multiple value types (e.g., `string \| number`) preserve the full `anyOf` array instead of flattening to the first type |
61
+
62
+<Accordions>
63
+<Accordion title="Toolkits with multi-type union fields (157 total)">
64
+
65
+### CRM & Sales
66
+active_campaign, apollo, attio, autobound, capsule_crm, firmao, forcemanager, gong, hubspot, instantly, intercom, kommo, leadfeeder, lever, magnetic, pipedrive, pipeline_crm, salesforce, salesforce_service_cloud, zoominfo
67
+
68
+### Marketing & Email
69
+active_trail, beamer, delighted, dripcel, enginemailer, mailerlite, moosend, mopinion, sendspark, toneden
70
+
71
+### Communication & Collaboration
72
+chmeetings, discord, helpdesk, helpwise, missive, slack, textit
73
+
74
+### Productivity & Project Management
75
+basecamp, clicksend, clientary, dart, fibery, monday, notion, onedesk, productboard, rocketlane, todoist
76
+
77
+### Developer Tools & APIs
78
+algolia, anonyflow, api_ninjas, api_sports, apify, appdrag, backendless, browserless, bubble, cloudconvert, cloudinary, cloudlayer, convertapi, databricks, datadog, datarobot, deepseek, deployhq, digital_ocean, docmosis, docugenerate, encodian, gitea, gitlab, globalping, groqcloud, hookdeck, hyperbrowser, imgbb, imgix, kibana, neutrino, npm, openai, openrouter, parsera, parseur, phantombuster, pinecone, prismic, procfu, replicate, scrape_do, serpapi, shotstack, snowflake, supabase, tavily, v0, vercel, writer, zenrows
79
+
80
+### E-commerce & Payments
81
+brex, btcpay_server, coupa, flutterwave, gift_up, lemon_squeezy, quaderno, ramp, shopify, stripe, zoho_invoice
82
+
83
+### HR & Recruiting
84
+ashby, bamboohr, recruitee
85
+
86
+### Data & Analytics
87
+amplitude, census_bureau, college_football_data, currencyscoop, diffbot, ip2location, mixpanel, nasa, rosette_text_analytics, securitytrails, textrazor, twelve_data
88
+
89
+### Documents & Files
90
+carbone, doc_certs, documenso, dropbox, excel, files_com, grist, pdf_co, share_point
91
+
92
+### Design & Media
93
+canva, canvas, claid_ai, deepimage, heygen, metatextai
94
+
95
+### Customer Support
96
+freshdesk, retently, servicem8, sevdesk, storeganise
97
+
98
+### Calendar & Scheduling
99
+calendly, deadline_funnel, etermin, googlecalendar
100
+
101
+### Social Media
102
+facebook, instagram, reddit
103
+
104
+### Location & Maps
105
+addresszen, geoapify, google_maps, mapbox
106
+
107
+### Email Verification & Validation
108
+clearout, icypeas, neverbounce, zerobounce
109
+
110
+### Other Integrations
111
+bitwarden, canny, cardly, castingwords, confluence, formdesk, getform, habitica, headout, highergov, jira, keen_io, landbot, moonclerk, one_drive, outlook, googlesheets, resend, ritekit, sms_alert, tapfiliate, thanks_io, uptimerobot
112
+
113
+</Accordion>
114
+</Accordions>
115
+
116
+### Before vs After
117
+For example, the `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` request schema changes:
118
+
119
+**Previous (only a single type):**
120
+```json
121
+{
122
+ "timezone": {
123
+ "default": 0,
124
+ "description": "Timezone specification...",
125
+ "title": "Timezone",
126
+ "type": "string"
127
+ }
128
+}
129
+```
130
+
131
+**Now (Union types preserved):**
132
+```json
133
+{
134
+ "timezone": {
135
+ "anyOf": [
136
+ { "type": "string" },
137
+ { "type": "number" }
138
+ ],
139
+ "default": 0,
140
+ "description": "Timezone specification...",
141
+ "title": "Timezone"
142
+ }
143
+}
144
+```
145
+
146
+Similarly, nullable fields like `page_token` in `GOOGLECALENDAR_LIST_CALENDARS`:
147
+
148
+**Previous:**
149
+```json
150
+{
151
+ "page_token": {
152
+ "default": null,
153
+ "description": "Token for the page of results to return...",
154
+ "nullable": true,
155
+ "title": "Page Token",
156
+ "type": "string"
157
+ }
158
+}
159
+```
160
+
161
+**Now:**
162
+```json
163
+{
164
+ "page_token": {
165
+ "anyOf": [
166
+ { "type": "string" },
167
+ { "type": "null" }
168
+ ],
169
+ "default": null,
170
+ "description": "Token for the page of results to return...",
171
+ "title": "Page Token"
172
+ }
173
+}
174
+```
175
+
176
+### Why This Matters
177
+
178
+- **Accurate schemas**: LLMs and code generators see the full set of allowed types
179
+- **Better validation**: Input validation can now correctly accept all valid types, not just the first one
fumadocs/content/changelog/01-08-26-mcp-api-key-enforcement.mdx
new
+142
@@ -0,0 +1,142 @@
1
+---
2
+title: "Optional API Key Enforcement for MCP Servers"
3
+date: "2026-01-08"
4
+---
5
+
6
+We've introduced a new project-level security setting that allows you to require API key authentication for all MCP server requests. This opt-in feature gives you fine-grained control over who can access your MCP endpoints.
7
+
8
+<Callout type="info">
9
+**Opt-in today, default soon**: This feature is currently opt-in. Starting **March 1, 2026**, it will be enabled by default for new organizations. We recommend enabling it now to prepare your integrations.
10
+</Callout>
11
+
12
+## What's New
13
+
14
+A new **"Require API Key for MCP"** toggle is now available in your Project Settings. When enabled, all requests to your MCP servers must include a valid Composio API key in the request headers.
15
+
16
+| Setting | Default | Impact |
17
+|---------|---------|--------|
18
+| `require_mcp_api_key` | `false` | Opt-in; no changes to existing behavior |
19
+
20
+## How It Works
21
+
22
+When the setting is **disabled** (default):
23
+- MCP servers work without API key authentication
24
+- Existing integrations continue to function unchanged
25
+
26
+When the setting is **enabled**:
27
+- All MCP requests must include the `x-api-key` header with a valid Composio API key
28
+- Requests without a valid API key receive `401 Unauthorized`
29
+- Only API keys belonging to the same project are accepted
30
+
31
+### Request Examples
32
+
33
+**Without API key (when enforcement is enabled):**
34
+```bash
35
+curl -X POST "https://mcp.composio.dev/{your_mcp_server_url}" \
36
+ -H "Content-Type: application/json" \
37
+ -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'
38
+
39
+# Response: 401 Unauthorized
40
+```
41
+
42
+**With API key:**
43
+```bash
44
+curl -X POST "https://mcp.composio.dev/{your_mcp_server_url}" \
45
+ -H "Content-Type: application/json" \
46
+ -H "x-api-key: ak_your_api_key" \
47
+ -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'
48
+
49
+# Response: 200 OK
50
+```
51
+
52
+## Enabling the Setting
53
+
54
+### Via Dashboard
55
+
56
+1. Navigate to [Project Settings](https://platform.composio.dev/{workspace}/{project}/settings)
57
+2. Go to the **Project Configuration** tab
58
+3. Find the **"Require API Key for MCP"** toggle
59
+4. Enable the toggle
60
+
61
+### Via API
62
+
63
+Update your project configuration using the API:
64
+
65
+```bash
66
+curl -X PATCH "https://backend.composio.dev/api/v3/org/project/config" \
67
+ -H "Content-Type: application/json" \
68
+ -H "x-api-key: ak_your_api_key" \
69
+ -d '{"require_mcp_api_key": true}'
70
+```
71
+
72
+**Response:**
73
+```json
74
+{
75
+ "require_mcp_api_key": true,
76
+ "is_2FA_enabled": true,
77
+ "mask_secret_keys_in_connected_account": true,
78
+ "log_visibility_setting": "show_all"
79
+}
80
+```
81
+
82
+### Via Code
83
+
84
+```python title="Python"
85
+import requests
86
+
87
+response = requests.patch(
88
+ "https://backend.composio.dev/api/v3/org/project/config",
89
+ headers={
90
+ "Content-Type": "application/json",
91
+ "x-api-key": "ak_your_api_key"
92
+ },
93
+ json={"require_mcp_api_key": True}
94
+)
95
+
96
+print(response.json())
97
+```
98
+
99
+```typescript title="TypeScript"
100
+const response = await fetch(
101
+ "https://backend.composio.dev/api/v3/org/project/config",
102
+ {
103
+ method: "PATCH",
104
+ headers: {
105
+ "Content-Type": "application/json",
106
+ "x-api-key": "ak_your_api_key"
107
+ },
108
+ body: JSON.stringify({ require_mcp_api_key: true })
109
+ }
110
+);
111
+
112
+console.log(await response.json());
113
+```
114
+
115
+## When to Use This
116
+
117
+Enable API key enforcement when you need to:
118
+
119
+- **Prevent unauthorized access** to your MCP servers
120
+- **Control which applications** can interact with your MCP endpoints
121
+- **Add an extra security layer** for production deployments
122
+- **Audit and track** MCP server usage through API key attribution
123
+
124
+## API Reference
125
+
126
+### Get Current Setting
127
+
128
+```http
129
+GET /api/v3/org/project/config
130
+```
131
+
132
+### Update Setting
133
+
134
+```http
135
+PATCH /api/v3/org/project/config
136
+```
137
+
138
+```json
139
+{
140
+ "require_mcp_api_key": true
141
+}
142
+```
fumadocs/content/changelog/01-09-26.mdx
new
+110
@@ -0,0 +1,110 @@
1
+---
2
+title: "Tool Enum Name Shortening"
3
+date: "2026-01-09"
4
+---
5
+
6
+Shortened tool enum names across 181 actions to ensure compatibility with all AI agent frameworks.
7
+
8
+## Why This Change?
9
+
10
+Some agent frameworks have a **64-character limit** on tool/function names. Several tool enums exceeded this limit, causing compatibility issues.
11
+
12
+## No Action Required
13
+
14
+**This change will not break your integration if you are using `latest` toolkit versions** or fetching tools dynamically. The SDK automatically resolves the correct tool names.
15
+
16
+<Accordions>
17
+<Accordion title="View All Enum Changes (181 tools)">
18
+
19
+| Old Enum | New Enum |
20
+|----------|----------|
21
+| `ACTIVE_TRAIL_GET_ACCOUNT_INTEGRATIONDATA_ACTIVECOMMERCE` | `ACTIVE_TRAIL_GET_ACCOUNT_INTEGRATIONDATA` |
22
+| `ACTIVE_TRAIL_GET_AUTOMATION_REPORTS_SMS_CAMPAIGN_SUMMARY_REPORT` | `ACTIVE_TRAIL_GET_AUTOMATION_REPORTS_SMS_CAMPAIGN_SUMMARY` |
23
+| `BIG_DATA_CLOUD_REVERSE_GEOCODING_WITH_TIMEZONE_API` | `BIG_DATA_CLOUD_REVERSE_GEOCODING_TIMEZONE_API` |
24
+| `CLICKSEND_RECHARGE_TRANSACTIONS_BY_TRANSACTION_ID_GET` | `CLICKSEND_RECHARGE_TXNS_BY_TXN_ID_GET` |
25
+| `CODEMAGIC_API_V3_VARIABLE_GROUPS_VARIABLE_GROUP_ID_UPDATE_GROUP` | `CODEMAGIC_API_V3_VARIABLE_GROUPS_VARIABLE_GROUP_ID_UPDATE` |
26
+| `COUPA_GET_ALL_FUNDS_TRANSFERS_IN_A_SPECIFIC_PAYMENT_BATCH_BY_PAYMENT_BATCH_ID` | `COUPA_GET_ALL_FUNDS_TRANSFERS_SPECIFIC_PAYMENT_BATCH` |
27
+| `COUPA_GET_PO_CONFIRMATION_IN_CANCELLED_STATUS_AND_NOT_EXPORTED` | `COUPA_GET_PO_CONFIRMATION_CANCELLED_STATUS_NOT_EXPORTED` |
28
+| `DATABRICKS_CATALOG_CREDENTIALS_GENERATE_TEMPORARY_SERVICE_CREDENTIAL` | `DATABRICKS_CATALOG_CREDS_GENERATE_TEMP_SERVICE_CRED` |
29
+| `DATABRICKS_CATALOG_CREDENTIALS_VALIDATE_CREDENTIAL` | `DATABRICKS_CATALOG_CREDS_VALIDATE_CRED` |
30
+| `DATABRICKS_CATALOG_EXTERNAL_METADATA_UPDATE_EXTERNAL_METADATA` | `DATABRICKS_CATALOG_EXTERNAL_METADATA_UPDATE_EXTERNAL` |
31
+| `DATABRICKS_CATALOG_RFA_GET_ACCESS_REQUEST_DESTINATIONS` | `DATABRICKS_CATALOG_RFA_GET_ACCESS_REQUEST_DESTS` |
32
+| `DATABRICKS_CATALOG_RFA_UPDATE_ACCESS_REQUEST_DESTINATIONS` | `DATABRICKS_CATALOG_RFA_UPDATE_ACCESS_REQUEST_DESTS` |
33
+| `DATABRICKS_CATALOG_TEMPORARY_PATH_CREDENTIALS_GENERATE_TEMPORARY_PATH_CREDENTIALS` | `DATABRICKS_CATALOG_TEMP_PATH_CREDS_GENERATE_TEMP_PATH_CREDS` |
34
+| `DATABRICKS_COMPUTE_CLUSTER_POLICIES_GET_PERMISSION_LEVELS` | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_GET_PERM_LEVELS` |
35
+| `DATABRICKS_COMPUTE_CLUSTER_POLICIES_GET_PERMISSIONS` | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_GET_PERMS` |
36
+| `DATABRICKS_COMPUTE_CLUSTER_POLICIES_SET_PERMISSIONS` | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_SET_PERMS` |
37
+| `DATABRICKS_COMPUTE_CLUSTER_POLICIES_UPDATE_PERMISSIONS` | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_UPDATE_PERMS` |
38
+| `DATABRICKS_COMPUTE_INSTANCE_POOLS_GET_PERMISSION_LEVELS` | `DATABRICKS_COMPUTE_INSTANCE_POOLS_GET_PERM_LEVELS` |
39
+| `DATABRICKS_COMPUTE_INSTANCE_POOLS_UPDATE_PERMISSIONS` | `DATABRICKS_COMPUTE_INSTANCE_POOLS_UPDATE_PERMS` |
40
+| `DATABRICKS_COMPUTE_POLICY_COMPLIANCE_FOR_CLUSTERS_ENFORCE_COMPLIANCE` | `DATABRICKS_COMPUTE_POLICY_COMPL_FOR_CLUSTERS_ENFORCE_COMPL` |
41
+| `DATABRICKS_COMPUTE_POLICY_COMPLIANCE_FOR_CLUSTERS_GET_COMPLIANCE` | `DATABRICKS_COMPUTE_POLICY_COMPL_FOR_CLUSTERS_GET_COMPL` |
42
+| `DATABRICKS_DASHBOARDS_GENIE_DELETE_CONVERSATION_MESSAGE` | `DATABRICKS_DASHBOARDS_GENIE_DELETE_CONV_MESSAGE` |
43
+| `DATABRICKS_DASHBOARDS_GENIE_EXECUTE_MESSAGE_ATTACHMENT_QUERY` | `DATABRICKS_DASHBOARDS_GENIE_EXECUTE_MESSAGE_ATTACH_QUERY` |
44
+| `DATABRICKS_DASHBOARDS_GENIE_GET_MESSAGE_ATTACHMENT_QUERY_RESULT` | `DATABRICKS_DASHBOARDS_GENIE_GET_MESSAGE_ATTACH_QUERY_RESULT` |
45
+| `DATABRICKS_DASHBOARDS_GENIE_GET_MESSAGE_QUERY_RESULT_BY_ATTACHMENT` | `DATABRICKS_DASHBOARDS_GENIE_GET_MESSAGE_QUERY_RESULT_ATTACH` |
46
+| `DATABRICKS_DASHBOARDS_GENIE_LIST_CONVERSATION_MESSAGES` | `DATABRICKS_DASHBOARDS_GENIE_LIST_CONV_MESSAGES` |
47
+| `DATABRICKS_DASHBOARDS_LAKEVIEW_EMBEDDED_GET_PUBLISHED_DASHBOARD_TOKEN_INFO` | `DATABRICKS_DASHBOARDS_LAKEVIEW_EMBEDDED_GET_PUBLISHED_DASH` |
48
+| `DATABRICKS_DATABASE_DATABASE_GENERATE_DATABASE_CREDENTIAL` | `DATABRICKS_DATABASE_DATABASE_GENERATE_DATABASE_CRED` |
49
+| `DATABRICKS_IAM_PERMISSION_MIGRATION_MIGRATE_PERMISSIONS` | `DATABRICKS_IAM_PERM_MIGRATION_MIGRATE_PERMS` |
50
+| `DATABRICKS_IAMV2_WORKSPACE_IAM_V2_GET_WORKSPACE_ACCESS_DETAIL_LOCAL` | `DATABRICKS_IAMV2_WORKSPACE_IAM_V2_GET_WORKSPACE_ACCESS` |
51
+| `DATABRICKS_JOB_PERMISSION_LEVELS_GETPERMISSIONLEVELS` | `DATABRICKS_JOB_PERM_LEVELS_GETPERMISSIONLEVELS` |
52
+| `DATABRICKS_JOBS_POLICY_COMPLIANCE_FOR_JOBS_GET_COMPLIANCE` | `DATABRICKS_JOBS_POLICY_COMPL_FOR_JOBS_GET_COMPL` |
53
+| `DATABRICKS_MARKETPLACE_CONSUMER_INSTALLATIONS_CREATE` | `DATABRICKS_MKTPLACE_CONSUMER_INSTALLATIONS_CREATE` |
54
+| `DATABRICKS_MARKETPLACE_CONSUMER_INSTALLATIONS_DELETE` | `DATABRICKS_MKTPLACE_CONSUMER_INSTALLATIONS_DELETE` |
55
+| `DATABRICKS_MARKETPLACE_CONSUMER_INSTALLATIONS_UPDATE` | `DATABRICKS_MKTPLACE_CONSUMER_INSTALLATIONS_UPDATE` |
56
+| `DATABRICKS_MARKETPLACE_CONSUMER_LISTINGS_BATCH_GET` | `DATABRICKS_MKTPLACE_CONSUMER_LISTINGS_BATCH_GET` |
57
+| `DATABRICKS_MARKETPLACE_CONSUMER_PERSONALIZATION_REQUESTS_GET` | `DATABRICKS_MKTPLACE_CONSUMER_PERSONALIZATION_REQUESTS_GET` |
58
+| `DATABRICKS_MARKETPLACE_CONSUMER_PROVIDERS_BATCH_GET` | `DATABRICKS_MKTPLACE_CONSUMER_PROVIDERS_BATCH_GET` |
59
+| `DATABRICKS_MARKETPLACE_PROVIDER_EXCHANGES_DELETE_LISTING_FROM_EXCHANGE` | `DATABRICKS_MKTPLACE_PROVIDER_EXCHANGES_DELETE_LISTING` |
60
+| `DATABRICKS_MARKETPLACE_PROVIDER_PROVIDER_ANALYTICS_DASHBOARDS_CREATE` | `DATABRICKS_MKTPLACE_PROVIDER_ANALYTICS_DASHBOARDS_CREATE` |
61
+| `DATABRICKS_MARKETPLACE_PROVIDER_PROVIDER_ANALYTICS_DASHBOARDS_GET` | `DATABRICKS_MKTPLACE_PROVIDER_ANALYTICS_DASHBOARDS_GET` |
62
+| `DATABRICKS_MARKETPLACE_PROVIDER_PROVIDER_ANALYTICS_DASHBOARDS_GET_LATEST_VERSION` | `DATABRICKS_MKTPLACE_PROVIDER_ANALYTICS_DASH_GET_LATEST` |
63
+| `DATABRICKS_ML_FEATURE_ENGINEERING_DELETE_KAFKA_CONFIG` | `DATABRICKS_ML_FEATURE_ENG_DELETE_KAFKA_CONFIG` |
64
+| `DATABRICKS_ML_MATERIALIZED_FEATURES_DELETE_FEATURE_TAG` | `DATABRICKS_ML_MAT_FEATURES_DELETE_FEATURE_TAG` |
65
+| `DATABRICKS_ML_MATERIALIZED_FEATURES_GET_FEATURE_TAG` | `DATABRICKS_ML_MAT_FEATURES_GET_FEATURE_TAG` |
66
+| `DATABRICKS_ML_MATERIALIZED_FEATURES_UPDATE_FEATURE_TAG` | `DATABRICKS_ML_MAT_FEATURES_UPDATE_FEATURE_TAG` |
67
+| `DATABRICKS_ML_MODEL_REGISTRY_GET_PERMISSION_LEVELS` | `DATABRICKS_ML_MODEL_REGISTRY_GET_PERM_LEVELS` |
68
+| `DATABRICKS_PIPELINES_PIPELINES_GET_PERMISSION_LEVELS` | `DATABRICKS_PIPELINES_PIPELINES_GET_PERM_LEVELS` |
69
+| `DATABRICKS_QUALITYMONITORV2_QUALITY_MONITOR_V2_CREATE_QUALITY_MONITOR` | `DATABRICKS_QUALITYMONITORV2_QUALITY_MONITOR_V2_CREATE` |
70
+| `DATABRICKS_SERVING_SERVING_ENDPOINTS_CREATE_PROVISIONED_THROUGHPUT_ENDPOINT` | `DATABRICKS_SERVING_SERVING_ENDPOINTS_CREATE_PROV_THPUT` |
71
+| `DATABRICKS_SERVING_SERVING_ENDPOINTS_GET_PERMISSION_LEVELS` | `DATABRICKS_SERVING_SERVING_ENDPOINTS_GET_PERM_LEVELS` |
72
+| `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_ACCESS_POLICY_DELETE` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_ACCESS_POLICY_DELETE` |
73
+| `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_ACCESS_POLICY_GET` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_ACCESS_POLICY_GET` |
74
+| `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_ACCESS_POLICY_UPDATE` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_ACCESS_POLICY_UPDATE` |
75
+| `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_APPROVED_DOMAINS_DELETE` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_DOMAINS_DELETE` |
76
+| `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_APPROVED_DOMAINS_GET` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_APPROVED_DOMAINS_GET` |
77
+| `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_APPROVED_DOMAINS_UPDATE` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_DOMAINS_UPDATE` |
78
+| `DATABRICKS_SETTINGS_COMPLIANCE_SECURITY_PROFILE_GET` | `DATABRICKS_SETTINGS_COMPL_SECURITY_PROFILE_GET` |
79
+| `DATABRICKS_SETTINGS_DASHBOARD_EMAIL_SUBSCRIPTIONS_DELETE` | `DATABRICKS_SETTINGS_DASH_EMAIL_SUBS_DELETE` |
80
+| `DATABRICKS_SETTINGS_DASHBOARD_EMAIL_SUBSCRIPTIONS_GET` | `DATABRICKS_SETTINGS_DASH_EMAIL_SUBS_GET` |
81
+| `DATABRICKS_SETTINGS_DASHBOARD_EMAIL_SUBSCRIPTIONS_UPDATE` | `DATABRICKS_SETTINGS_DASH_EMAIL_SUBS_UPDATE` |
82
+| `DATABRICKS_SETTINGS_ENABLE_EXPORT_NOTEBOOK_GET_ENABLE_EXPORT_NOTEBOOK` | `DATABRICKS_SETTINGS_ENABLE_EXPORT_NOTEBOOK_GET_ENABLE` |
83
+| `DATABRICKS_SETTINGS_ENABLE_EXPORT_NOTEBOOK_PATCH_ENABLE_EXPORT_NOTEBOOK` | `DATABRICKS_SETTINGS_ENABLE_EXPORT_NOTEBOOK_PATCH_ENABLE` |
84
+| `DATABRICKS_SETTINGS_ENABLE_NOTEBOOK_TABLE_CLIPBOARD_GET_ENABLE_NOTEBOOK_TABLE_CLIPBOARD` | `DATABRICKS_SETTINGS_ENABLE_NOTEBOOK_TABLE_CLIPBOARD_GET` |
85
+| `DATABRICKS_SETTINGS_ENABLE_NOTEBOOK_TABLE_CLIPBOARD_PATCH_ENABLE_NOTEBOOK_TABLE_CLIPBOARD` | `DATABRICKS_SETTINGS_ENABLE_NOTEBOOK_TABLE_CLIPBOARD_PATCH` |
86
+| `DATABRICKS_SETTINGS_ENABLE_RESULTS_DOWNLOADING_GET_ENABLE_RESULTS_DOWNLOADING` | `DATABRICKS_SETTINGS_ENABLE_RESULTS_DOWNLOADING_GET_ENABLE` |
87
+| `DATABRICKS_SETTINGS_LLM_PROXY_PARTNER_POWERED_WORKSPACE_DELETE` | `DATABRICKS_SETTINGS_LLM_PROXY_PARTNER_WORKSPACE_DELETE` |
88
+| `DATABRICKS_SETTINGS_LLM_PROXY_PARTNER_POWERED_WORKSPACE_UPDATE` | `DATABRICKS_SETTINGS_LLM_PROXY_PARTNER_WORKSPACE_UPDATE` |
89
+| `DATABRICKS_SETTINGS_NOTIFICATION_DESTINATIONS_CREATE` | `DATABRICKS_SETTINGS_NOTIF_DESTS_CREATE` |
90
+| `DATABRICKS_SETTINGS_NOTIFICATION_DESTINATIONS_DELETE` | `DATABRICKS_SETTINGS_NOTIF_DESTS_DELETE` |
91
+| `DATABRICKS_SETTINGS_NOTIFICATION_DESTINATIONS_UPDATE` | `DATABRICKS_SETTINGS_NOTIF_DESTS_UPDATE` |
92
+| `DATABRICKS_SETTINGS_TOKEN_MANAGEMENT_GET_PERMISSION_LEVELS` | `DATABRICKS_SETTINGS_TOKEN_MGMT_GET_PERM_LEVELS` |
93
+| `DATABRICKS_SETTINGS_TOKEN_MANAGEMENT_GET_PERMISSIONS` | `DATABRICKS_SETTINGS_TOKEN_MGMT_GET_PERMS` |
94
+| `DATABRICKS_SETTINGS_TOKEN_MANAGEMENT_SET_PERMISSIONS` | `DATABRICKS_SETTINGS_TOKEN_MGMT_SET_PERMS` |
95
+| `DATABRICKS_SETTINGS_TOKEN_MANAGEMENT_UPDATE_PERMISSIONS` | `DATABRICKS_SETTINGS_TOKEN_MGMT_UPDATE_PERMS` |
96
+| `DATABRICKS_SETTINGSV2_WORKSPACE_SETTINGS_V2_GET_PUBLIC_WORKSPACE_SETTING` | `DATABRICKS_SETTINGSV2_WORKSPACE_SETTINGS_V2_GET_PUBLIC` |
97
+| `DATABRICKS_SQL_STATEMENT_EXECUTION_CANCEL_EXECUTION` | `DATABRICKS_SQL_STATEMENT_EXEC_CANCEL_EXEC` |
98
+| `DATABRICKS_VECTORSEARCH_VECTOR_SEARCH_ENDPOINTS_CREATE_ENDPOINT` | `DATABRICKS_VECTORSEARCH_VECTOR_SEARCH_ENDPOINTS_CREATE` |
99
+| `DATABRICKS_VECTORSEARCH_VECTOR_SEARCH_INDEXES_UPSERT_DATA_VECTOR_INDEX` | `DATABRICKS_VECTORSEARCH_VECTOR_SEARCH_INDEXES_UPSERT_DATA` |
100
+| `DEPLOYHQ_DELETE_PROJECTS_PROJECT_BUILD_CACHE_FILES_IDENTIFIER` | `DEPLOYHQ_DELETE_PROJECTS_PROJECT_BUILD_CACHE_FILES` |
101
+| `DROPBOX_SIGN_EDIT_AND_RESEND_EMBEDDED_SIGNATURE_REQUEST_WITH_TEMPLATE` | `DROPBOX_SIGN_EDIT_RESEND_EMBEDDED_SIGNATURE_REQUEST_TEMPLATE` |
102
+| `GITHUB_CREATE_OR_UPDATE_CUSTOM_PROPERTIES_FOR_AN_ORGANIZATION` | `GITHUB_CREATE_OR_UPDATE_CUSTOM_PROPERTIES_FOR_AN_ORG` |
103
+| ... and 100+ more |
104
+
105
+</Accordion>
106
+</Accordions>
107
+
108
+## Migration
109
+
110
+If you're referencing any affected tool enums by their old names, update to the new shortened names.
fumadocs/content/changelog/01-12-26-tool-router-improvements.mdx
new
+129
@@ -0,0 +1,129 @@
1
+---
2
+title: "Tool Router Improvements and New Features"
3
+date: "2026-01-12"
4
+---
5
+
6
+## Version Information
7
+
8
+### TypeScript/JavaScript
9
+- Package: `@composio/core` and provider packages
10
+- Version: `0.3.4` to `0.4.0`
11
+
12
+### Python
13
+- Package: `composio-core` and provider packages
14
+- Version: `0.10.4` to `0.10.5`
15
+
16
+## New Features
17
+
18
+### 1. Wait for Connections Property
19
+
20
+Added `waitForConnections` (TypeScript) / `wait_for_connections` (Python) property to manage connections configuration. This allows tool router sessions to wait for users to complete authentication before proceeding to the next step.
21
+
22
+**TypeScript:**
23
+```typescript
24
+const session = await composio.toolRouter.create(userId, {
25
+ manageConnections: {
26
+ enable: true,
27
+ callbackUrl: 'https://example.com/callback',
28
+ waitForConnections: true // NEW
29
+ }
30
+});
31
+```
32
+
33
+**Python:**
34
+```python
35
+session = tool_router.create(
36
+ user_id="user_123",
37
+ manage_connections={
38
+ "enable": True,
39
+ "callback_url": "https://example.com/callback",
40
+ "wait_for_connections": True # NEW
41
+ }
42
+)
43
+```
44
+
45
+### 2. Session-Specific Modifier Types
46
+
47
+Introduced new modifier types for better session-based tool execution: `SessionExecuteMetaModifiers` and `SessionMetaToolOptions`.
48
+
49
+**TypeScript:**
50
+```typescript
51
+const tools = await session.tools({
52
+ modifySchema: ({ toolSlug, toolkitSlug, schema }) => schema,
53
+ beforeExecute: ({ toolSlug, toolkitSlug, sessionId, params }) => params,
54
+ afterExecute: ({ toolSlug, toolkitSlug, sessionId, result }) => result
55
+});
56
+```
57
+
58
+**Python:**
59
+```python
60
+from composio.core.models import before_execute_meta, after_execute_meta
61
+
62
+@before_execute_meta
63
+def before_modifier(tool, toolkit, session_id, params):
64
+ return params
65
+
66
+@after_execute_meta
67
+def after_modifier(tool, toolkit, session_id, response):
68
+ return response
69
+
70
+tools = session.tools(modifiers=[before_modifier, after_modifier])
71
+```
72
+
73
+### 3. Dedicated Method for Tool Router Meta Tools
74
+
75
+Added `getRawToolRouterMetaTools` (TypeScript) / `get_raw_tool_router_meta_tools` (Python) method in the Tools class for fetching meta tools directly from a tool router session.
76
+
77
+**TypeScript:**
78
+```typescript
79
+const metaTools = await composio.tools.getRawToolRouterMetaTools('session_123', {
80
+ modifySchema: ({ toolSlug, toolkitSlug, schema }) => {
81
+ // Customize schema
82
+ return schema;
83
+ }
84
+});
85
+```
86
+
87
+**Python:**
88
+```python
89
+meta_tools = tools_model.get_raw_tool_router_meta_tools(
90
+ session_id="session_123",
91
+ modifiers=[schema_modifier]
92
+)
93
+```
94
+
95
+## Internal Improvements
96
+
97
+### 1. Performance Optimization
98
+
99
+Eliminated unnecessary tool fetching during tool router execution, resulting in faster tool execution with fewer API calls.
100
+
101
+### 2. Improved Architecture
102
+
103
+Tool router sessions now fetch tools directly from the session API endpoint instead of using tool slugs, providing better consistency and reliability.
104
+
105
+### 3. Simplified Implementation
106
+
107
+Removed redundant tool schema fetching in execution paths, using a hardcoded 'composio' toolkit slug for meta tools.
108
+
109
+## Backward Compatibility
110
+
111
+This release is fully backward compatible:
112
+
113
+- All existing code continues to work without modifications
114
+- New properties are optional with sensible defaults
115
+- New modifier types can be adopted incrementally
116
+- Internal changes have no impact on public APIs
117
+- No migration required
118
+
119
+## Impact Summary
120
+
121
+| Change | Runtime Breaking | TypeScript Breaking | Migration Required |
122
+|--------|------------------|---------------------|-------------------|
123
+| `wait_for_connections` property | No | No | No |
124
+| Session-specific modifiers | No | No | No |
125
+| `getRawToolRouterMetaTools` method | No | No | No |
126
+| Tool router uses session API | No | No | No |
127
+| Optimized tool execution | No | No | No |
128
+
129
+All changes follow semantic versioning principles and maintain full backward compatibility.
fumadocs/content/changelog/12-30-25-proxy-binary-data.mdx
new
+91
@@ -0,0 +1,91 @@
1
+---
2
+title: "Binary Data Support for Proxy Execute"
3
+date: "2025-12-30"
4
+---
5
+
6
+The `/api/v3/tools/execute/proxy` endpoint now supports binary data for both file uploads and downloads.
7
+
8
+### File Uploads (`binary_body`)
9
+
10
+To upload a file via the proxy, use the `binary_body` field in your request payload. This supports two approaches: specifying either a URL pointing to the file or providing the base64-encoded content directly.
11
+
12
+#### Upload File via URL
13
+
14
+```bash
15
+curl --location 'https://backend.composio.dev/api/v3/tools/execute/proxy' \
16
+ --header 'accept: application/json' \
17
+ --header 'x-api-key: <YOUR_API_KEY>' \
18
+ --header 'Content-Type: application/json' \
19
+ --data '{
20
+ "endpoint": "/upload-endpoint",
21
+ "method": "POST",
22
+ "connected_account_id": "<CONNECTED_ACCOUNT_ID>",
23
+ "binary_body": {
24
+ "url": "{URL_TO_THE_FILE}"
25
+ }
26
+ }'
27
+```
28
+
29
+#### Upload File via Base64 Content
30
+
31
+Supported up to 4MB file size.
32
+
33
+```bash
34
+curl --location 'https://backend.composio.dev/api/v3/tools/execute/proxy' \
35
+ --header 'accept: application/json' \
36
+ --header 'x-api-key: <YOUR_API_KEY>' \
37
+ --header 'Content-Type: application/json' \
38
+ --data '{
39
+ "endpoint": "/upload-endpoint",
40
+ "method": "POST",
41
+ "connected_account_id": "<CONNECTED_ACCOUNT_ID>",
42
+ "binary_body": {
43
+ "base64": "JVBERi0xLjQKJ...<base64_data>...",
44
+ "content_type": "application/pdf"
45
+ }
46
+ }'
47
+```
48
+
49
+### File Downloads (`binary_data`)
50
+
51
+When the proxied request returns a binary response (for example, a PDF or image), the proxy automatically uploads the file to temporary storage, and you receive a signed URL in the `binary_data` field. This enables you to download large files securely.
52
+
53
+#### File Download Request
54
+
55
+```bash
56
+curl --location 'https://backend.composio.dev/api/v3/tools/execute/proxy' \
57
+ --header 'accept: application/json' \
58
+ --header 'x-api-key: <YOUR_API_KEY>' \
59
+ --header 'Content-Type: application/json' \
60
+ --data '{
61
+ "endpoint": "{YOUR_ENDPOINT}",
62
+ "method": "GET",
63
+ "connected_account_id": "{YOUR_CONNECTED_ACCOUNT_ID}"
64
+ }'
65
+```
66
+
67
+#### File Download Response
68
+
69
+```json
70
+{
71
+ "data": {},
72
+ "binary_data": {
73
+ "url": "url to the file",
74
+ "content_type": "content type of the file",
75
+ "size": "size of the file",
76
+ "expires_at": "expires at of the file"
77
+ },
78
+ "status": "status code of the response",
79
+ "headers": "headers of the response"
80
+}
81
+```
82
+
83
+### Summary
84
+
85
+| Feature | Field | Description |
86
+|---------|-------|-------------|
87
+| File Upload via URL | `binary_body.url` | Provide a URL pointing to the file to upload |
88
+| File Upload via Base64 | `binary_body.base64` + `binary_body.content_type` | Provide base64-encoded content (up to 4MB) |
89
+| File Download | `binary_data` in response | Receive a signed URL to download binary responses |
90
+
91
+We'd love your feedback on the new proxy execute capabilities. If anything feels unclear or you have suggestions for improvement, please reach out.
fumadocs/content/changelog/12-30-25.mdx
new
+151
@@ -0,0 +1,151 @@
1
+---
2
+title: "Webhook Payload V3 - Lookahead Announcement"
3
+date: "2025-12-30"
4
+---
5
+
6
+We're introducing **Webhook Payload V3** - a redesigned webhook structure that follows industry standards and provides better developer experience. This update affects how you receive trigger events via webhooks and Pusher.
7
+
8
+## What's Changing?
9
+
10
+### New Webhook Structure
11
+
12
+We're adopting the [Standard Webhooks specification](https://github.com/standard-webhooks/standard-webhooks/blob/main/spec/standard-webhooks.md) for better consistency and reliability.
13
+
14
+#### Headers
15
+A new header will identify the webhook version:
16
+```
17
+x-composio-webhook-version: V3
18
+```
19
+
20
+#### Payload Structure
21
+The payload structure is being reorganized to separate Composio metadata from trigger data:
22
+
23
+**Before (V2):**
24
+```json
25
+{
26
+ "log_id": "log_TpxVOLXYnwXZ",
27
+ "timestamp": "2025-12-23T13:06:07.695Z",
28
+ "type": "gmail_new_gmail_message",
29
+ "data": {
30
+ "connection_id": "a1b2c3d4-5e6f-7a8b-9c0d-1e2f3a4b5c6d",
31
+ "connection_nano_id": "ca_xYz9AbCdEfGh",
32
+ "trigger_nano_id": "ti_JZFoTyYKbzhB",
33
+ "trigger_id": "7f8e9d0c-1b2a-3c4d-5e6f-7a8b9c0d1e2f",
34
+ "user_id": "usr-demo-12a3b4c5...",
35
+ // ... actual trigger data mixed with metadata
36
+ }
37
+}
38
+```
39
+
40
+**After (V3):**
41
+```json
42
+{
43
+ "id": "msg_a1b2c3d4-5e6f-7a8b-9c0d-1e2f3a4b5c6d",
44
+ "timestamp": "2025-12-23T13:06:07.695Z",
45
+ "type": "composio.trigger.message",
46
+ "metadata": {
47
+ "log_id": "log_TpxVOLXYnwXZ",
48
+ "trigger_slug": "GMAIL_NEW_GMAIL_MESSAGE",
49
+ "auth_config_id": "ac_aCYTppZ5RsRc",
50
+ "connected_account_id": "ca_cATYssZ5RrSc",
51
+ "trigger_id": "ti_JZFoTyYKbzhB",
52
+ "user_id": "pg-test-86c9fc84..."
53
+ },
54
+ "data": {
55
+ // Clean trigger data without Composio metadata
56
+ }
57
+}
58
+```
59
+
60
+### Key Improvements
61
+
62
+1. **Metadata Separation**: Composio-specific fields (connection IDs, trigger IDs, user IDs) are now in a dedicated `metadata` object
63
+2. **Clean Data**: The `data` field now contains only the actual trigger payload without infrastructure metadata
64
+3. **Standardized Type Field**: The `type` field now follows a consistent format (`composio.trigger.message`) instead of trigger-specific names like `gmail_new_gmail_message`
65
+4. **Trigger Slug in Metadata**: The trigger slug (e.g., `GMAIL_NEW_GMAIL_MESSAGE`) is now available in `metadata.trigger_slug` for easy identification
66
+5. **Standards Compliance**: Follows Standard Webhooks specification for better interoperability
67
+6. **Consistent Structure**: Same payload structure for both webhooks and Pusher channels
68
+
69
+## Migration Guide
70
+
71
+### Updating Your Webhook Handlers
72
+
73
+If you're accessing Composio metadata fields, update your code:
74
+
75
+```python
76
+# Before (V2)
77
+trigger_type = payload["type"] # "gmail_new_gmail_message"
78
+connection_id = payload["data"]["connection_id"]
79
+trigger_id = payload["data"]["trigger_id"]
80
+message_text = payload["data"]["message_text"]
81
+
82
+# After (V3)
83
+trigger_type = payload["type"] # "composio.trigger.message"
84
+trigger_slug = payload["metadata"]["trigger_slug"] # "GMAIL_NEW_GMAIL_MESSAGE"
85
+connection_id = payload["metadata"]["connected_account_id"]
86
+trigger_id = payload["metadata"]["trigger_id"]
87
+message_text = payload["data"]["message_text"]
88
+```
89
+
90
+```typescript
91
+// Before (V2)
92
+const triggerSlug = payload.type; // "gmail_new_gmail_message"
93
+const connectionId = payload.data.connection_id;
94
+const triggerId = payload.data.trigger_id;
95
+const messageText = payload.data.message_text;
96
+
97
+// After (V3)
98
+const webhookType = payload.type; // "composio.trigger.message"
99
+const triggerSlug = payload.metadata.trigger_slug; // "GMAIL_NEW_GMAIL_MESSAGE"
100
+const connectionId = payload.metadata.connected_account_id;
101
+const triggerId = payload.metadata.trigger_id;
102
+const messageText = payload.data.message_text;
103
+```
104
+
105
+### Checking Webhook Version
106
+
107
+You can detect the webhook version from headers:
108
+
109
+```python
110
+webhook_version = headers.get("x-composio-webhook-version", "V2")
111
+if webhook_version == "V3":
112
+ # Use new structure
113
+ metadata = payload["metadata"]
114
+else:
115
+ # Use old structure
116
+ metadata = payload["data"]
117
+```
118
+
119
+## Rollout Timeline
120
+
121
+- **December 2025**: V3 released, opt-in via project settings
122
+- **February 15, 2026**: All new organizations will default to V3
123
+- **Existing organizations**: Continue using V2 by default, can opt-in to V3 anytime
124
+
125
+## How to Opt-In
126
+
127
+1. Go to your project settings in the Composio dashboard
128
+2. Navigate to the Webhooks section
129
+3. Select "Webhook Payload Version: V3"
130
+4. Update your webhook handlers to use the new structure
131
+5. Test thoroughly before enabling in production
132
+
133
+<Callout type="info">
134
+Organizations created **before February 15, 2026** will remain on V2 by default. You can switch to V3 at your convenience.
135
+
136
+Organizations created **on or after February 15, 2026** will use V3 by default.
137
+</Callout>
138
+
139
+## Benefits
140
+
141
+- **Better DX**: Clear separation between metadata and actual trigger data
142
+- **Standards Compliance**: Follows industry-standard webhook specifications
143
+- **Consistency**: Same structure across webhooks and Pusher channels
144
+- **Future-Proof**: Built on established standards for long-term compatibility
145
+
146
+## Need Help?
147
+
148
+If you have questions about migrating to V3 or need assistance:
149
+- Join our [Discord community](https://discord.gg/composio)
150
+- Check our [documentation](https://docs.composio.dev)
151
+- Contact support at support@composio.dev
fumadocs/content/changelog/12-31-25.mdx
new
+38
@@ -0,0 +1,38 @@
1
+---
2
+title: "Deprecating BEARER_TOKEN auth scheme for 19 toolkits"
3
+date: "2025-12-31"
4
+---
5
+
6
+We've **deprecated** the `BEARER_TOKEN` auth scheme for the following **19 toolkits**:
7
+
8
+- `Airtable`
9
+- `Discord`
10
+- `Discordbot`
11
+- `Gmail`
12
+- `Google Classroom`
13
+- `Google Search Console`
14
+- `Google Calendar`
15
+- `Google Docs`
16
+- `Google Drive`
17
+- `Google Slides`
18
+- `Google Super`
19
+- `Instagram`
20
+- `Ntfy`
21
+- `Sapling AI`
22
+- `Slack`
23
+- `Slackbot`
24
+- `Tawk To`
25
+- `TikTok`
26
+- `Twitter`
27
+
28
+### Recommendation
29
+
30
+For these toolkits, we recommend using **alternative auth schemes** (for example, `OAUTH2`, `API_KEY`, or other toolkit-supported schemes) instead of `BEARER_TOKEN`.
31
+
32
+### Backward compatibility (explicit)
33
+
34
+This change is **fully backward compatible**:
35
+
36
+- **Existing** auth configs and connected accounts created with `BEARER_TOKEN` **will continue to function**.
37
+- **Creating new** auth configs and connected accounts with `BEARER_TOKEN` **will continue to work** (e.g., via API/SDK).
38
+- To discourage new usage, `BEARER_TOKEN` auth configs / connected accounts **will not be displayed in the UI** for these toolkits.