Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
TypeScript agentic-aiagentsaiai-agentsaiagentsdeveloper-toolsfunction-callinggpt-4javascriptjsllmllmopsmcppythonremote-mcp-serverssetypescript
docs(fumadocs): sync missing changelogs from fern
Sushmithamalleshc3ca84a0f9fb
diff --git a/fumadocs/content/changelog/01-07-26.mdx b/fumadocs/content/changelog/01-07-26.mdxnew file mode 100644index 000000000..1a19ad46c--- /dev/null+++ b/fumadocs/content/changelog/01-07-26.mdx@@ -0,0 +1,179 @@+---+title: "Consistent Error Response Structure & Union Types Preserved"+date: "2026-01-07"+---++## Consistent Error Response Structure++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.++### What Changed++All error responses from tool execution now include:+- `data.status_code`: HTTP status code (or `null` for non-HTTP errors)+- `data.message`: Detailed error message+- `error`: Same detailed message at the top level++### Before vs After++**Previous error response:**+```json+{+ "data": {},+ "successfull": false,+ "error": "404 Client Error: Not Found for url: ...",+}+```++**New error response:**+```json+{+ "data": {+ "http_error": "404 Client Error: Not Found for url: ...",+ "status_code": 404,+ "message": "Resource not found: The requested item does not exist"+ },+ "successfull": false,+ "error": "Resource not found: The requested item does not exist",+}+```++### Why This Matters++- **Easier parsing**: Agents and code can reliably access error details from `data.message` without special-casing empty `data` objects+- **Better debugging**: Detailed error messages replace generic HTTP error strings+- **Consistent schema**: Same response shape whether the tool succeeds or fails++---++## Union Types Preserved in Tool Schemas++Tool schemas now use standard JSON Schema `anyOf` for union types, providing accurate type information for LLMs and code generators.++### What Changed++Two changes affect how types appear in request/response schemas:++| Change | Scope | Description |+|--------|-------|-------------|+| **Nullable fields** | **All toolkits** | Fields that accept `null` now use `anyOf: [{type}, {type: "null"}]` instead of `type` + `nullable: true` |+| **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 |++<Accordions>+<Accordion title="Toolkits with multi-type union fields (157 total)">++### CRM & Sales+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++### Marketing & Email+active_trail, beamer, delighted, dripcel, enginemailer, mailerlite, moosend, mopinion, sendspark, toneden++### Communication & Collaboration+chmeetings, discord, helpdesk, helpwise, missive, slack, textit++### Productivity & Project Management+basecamp, clicksend, clientary, dart, fibery, monday, notion, onedesk, productboard, rocketlane, todoist++### Developer Tools & APIs+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++### E-commerce & Payments+brex, btcpay_server, coupa, flutterwave, gift_up, lemon_squeezy, quaderno, ramp, shopify, stripe, zoho_invoice++### HR & Recruiting+ashby, bamboohr, recruitee++### Data & Analytics+amplitude, census_bureau, college_football_data, currencyscoop, diffbot, ip2location, mixpanel, nasa, rosette_text_analytics, securitytrails, textrazor, twelve_data++### Documents & Files+carbone, doc_certs, documenso, dropbox, excel, files_com, grist, pdf_co, share_point++### Design & Media+canva, canvas, claid_ai, deepimage, heygen, metatextai++### Customer Support+freshdesk, retently, servicem8, sevdesk, storeganise++### Calendar & Scheduling+calendly, deadline_funnel, etermin, googlecalendar++### Social Media+facebook, instagram, reddit++### Location & Maps+addresszen, geoapify, google_maps, mapbox++### Email Verification & Validation+clearout, icypeas, neverbounce, zerobounce++### Other Integrations+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++</Accordion>+</Accordions>++### Before vs After+For example, the `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` request schema changes:++**Previous (only a single type):**+```json+{+ "timezone": {+ "default": 0,+ "description": "Timezone specification...",+ "title": "Timezone",+ "type": "string"+ }+}+```++**Now (Union types preserved):**+```json+{+ "timezone": {+ "anyOf": [+ { "type": "string" },+ { "type": "number" }+ ],+ "default": 0,+ "description": "Timezone specification...",+ "title": "Timezone"+ }+}+```++Similarly, nullable fields like `page_token` in `GOOGLECALENDAR_LIST_CALENDARS`:++**Previous:**+```json+{+ "page_token": {+ "default": null,+ "description": "Token for the page of results to return...",+ "nullable": true,+ "title": "Page Token",+ "type": "string"+ }+}+```++**Now:**+```json+{+ "page_token": {+ "anyOf": [+ { "type": "string" },+ { "type": "null" }+ ],+ "default": null,+ "description": "Token for the page of results to return...",+ "title": "Page Token"+ }+}+```++### Why This Matters++- **Accurate schemas**: LLMs and code generators see the full set of allowed types+- **Better validation**: Input validation can now correctly accept all valid types, not just the first onediff --git a/fumadocs/content/changelog/01-08-26-mcp-api-key-enforcement.mdx b/fumadocs/content/changelog/01-08-26-mcp-api-key-enforcement.mdxnew file mode 100644index 000000000..43d85437f--- /dev/null+++ b/fumadocs/content/changelog/01-08-26-mcp-api-key-enforcement.mdx@@ -0,0 +1,142 @@+---+title: "Optional API Key Enforcement for MCP Servers"+date: "2026-01-08"+---++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.++<Callout type="info">+**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.+</Callout>++## What's New++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.++| Setting | Default | Impact |+|---------|---------|--------|+| `require_mcp_api_key` | `false` | Opt-in; no changes to existing behavior |++## How It Works++When the setting is **disabled** (default):+- MCP servers work without API key authentication+- Existing integrations continue to function unchanged++When the setting is **enabled**:+- All MCP requests must include the `x-api-key` header with a valid Composio API key+- Requests without a valid API key receive `401 Unauthorized`+- Only API keys belonging to the same project are accepted++### Request Examples++**Without API key (when enforcement is enabled):**+```bash+curl -X POST "https://mcp.composio.dev/{your_mcp_server_url}" \+ -H "Content-Type: application/json" \+ -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'++# Response: 401 Unauthorized+```++**With API key:**+```bash+curl -X POST "https://mcp.composio.dev/{your_mcp_server_url}" \+ -H "Content-Type: application/json" \+ -H "x-api-key: ak_your_api_key" \+ -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'++# Response: 200 OK+```++## Enabling the Setting++### Via Dashboard++1. Navigate to [Project Settings](https://platform.composio.dev/{workspace}/{project}/settings)+2. Go to the **Project Configuration** tab+3. Find the **"Require API Key for MCP"** toggle+4. Enable the toggle++### Via API++Update your project configuration using the API:++```bash+curl -X PATCH "https://backend.composio.dev/api/v3/org/project/config" \+ -H "Content-Type: application/json" \+ -H "x-api-key: ak_your_api_key" \+ -d '{"require_mcp_api_key": true}'+```++**Response:**+```json+{+ "require_mcp_api_key": true,+ "is_2FA_enabled": true,+ "mask_secret_keys_in_connected_account": true,+ "log_visibility_setting": "show_all"+}+```++### Via Code++```python title="Python"+import requests++response = requests.patch(+ "https://backend.composio.dev/api/v3/org/project/config",+ headers={+ "Content-Type": "application/json",+ "x-api-key": "ak_your_api_key"+ },+ json={"require_mcp_api_key": True}+)++print(response.json())+```++```typescript title="TypeScript"+const response = await fetch(+ "https://backend.composio.dev/api/v3/org/project/config",+ {+ method: "PATCH",+ headers: {+ "Content-Type": "application/json",+ "x-api-key": "ak_your_api_key"+ },+ body: JSON.stringify({ require_mcp_api_key: true })+ }+);++console.log(await response.json());+```++## When to Use This++Enable API key enforcement when you need to:++- **Prevent unauthorized access** to your MCP servers+- **Control which applications** can interact with your MCP endpoints+- **Add an extra security layer** for production deployments+- **Audit and track** MCP server usage through API key attribution++## API Reference++### Get Current Setting++```http+GET /api/v3/org/project/config+```++### Update Setting++```http+PATCH /api/v3/org/project/config+```++```json+{+ "require_mcp_api_key": true+}+```diff --git a/fumadocs/content/changelog/01-09-26.mdx b/fumadocs/content/changelog/01-09-26.mdxnew file mode 100644index 000000000..f91e21f7b--- /dev/null+++ b/fumadocs/content/changelog/01-09-26.mdx@@ -0,0 +1,110 @@+---+title: "Tool Enum Name Shortening"+date: "2026-01-09"+---++Shortened tool enum names across 181 actions to ensure compatibility with all AI agent frameworks.++## Why This Change?++Some agent frameworks have a **64-character limit** on tool/function names. Several tool enums exceeded this limit, causing compatibility issues.++## No Action Required++**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.++<Accordions>+<Accordion title="View All Enum Changes (181 tools)">++| Old Enum | New Enum |+|----------|----------|+| `ACTIVE_TRAIL_GET_ACCOUNT_INTEGRATIONDATA_ACTIVECOMMERCE` | `ACTIVE_TRAIL_GET_ACCOUNT_INTEGRATIONDATA` |+| `ACTIVE_TRAIL_GET_AUTOMATION_REPORTS_SMS_CAMPAIGN_SUMMARY_REPORT` | `ACTIVE_TRAIL_GET_AUTOMATION_REPORTS_SMS_CAMPAIGN_SUMMARY` |+| `BIG_DATA_CLOUD_REVERSE_GEOCODING_WITH_TIMEZONE_API` | `BIG_DATA_CLOUD_REVERSE_GEOCODING_TIMEZONE_API` |+| `CLICKSEND_RECHARGE_TRANSACTIONS_BY_TRANSACTION_ID_GET` | `CLICKSEND_RECHARGE_TXNS_BY_TXN_ID_GET` |+| `CODEMAGIC_API_V3_VARIABLE_GROUPS_VARIABLE_GROUP_ID_UPDATE_GROUP` | `CODEMAGIC_API_V3_VARIABLE_GROUPS_VARIABLE_GROUP_ID_UPDATE` |+| `COUPA_GET_ALL_FUNDS_TRANSFERS_IN_A_SPECIFIC_PAYMENT_BATCH_BY_PAYMENT_BATCH_ID` | `COUPA_GET_ALL_FUNDS_TRANSFERS_SPECIFIC_PAYMENT_BATCH` |+| `COUPA_GET_PO_CONFIRMATION_IN_CANCELLED_STATUS_AND_NOT_EXPORTED` | `COUPA_GET_PO_CONFIRMATION_CANCELLED_STATUS_NOT_EXPORTED` |+| `DATABRICKS_CATALOG_CREDENTIALS_GENERATE_TEMPORARY_SERVICE_CREDENTIAL` | `DATABRICKS_CATALOG_CREDS_GENERATE_TEMP_SERVICE_CRED` |+| `DATABRICKS_CATALOG_CREDENTIALS_VALIDATE_CREDENTIAL` | `DATABRICKS_CATALOG_CREDS_VALIDATE_CRED` |+| `DATABRICKS_CATALOG_EXTERNAL_METADATA_UPDATE_EXTERNAL_METADATA` | `DATABRICKS_CATALOG_EXTERNAL_METADATA_UPDATE_EXTERNAL` |+| `DATABRICKS_CATALOG_RFA_GET_ACCESS_REQUEST_DESTINATIONS` | `DATABRICKS_CATALOG_RFA_GET_ACCESS_REQUEST_DESTS` |+| `DATABRICKS_CATALOG_RFA_UPDATE_ACCESS_REQUEST_DESTINATIONS` | `DATABRICKS_CATALOG_RFA_UPDATE_ACCESS_REQUEST_DESTS` |+| `DATABRICKS_CATALOG_TEMPORARY_PATH_CREDENTIALS_GENERATE_TEMPORARY_PATH_CREDENTIALS` | `DATABRICKS_CATALOG_TEMP_PATH_CREDS_GENERATE_TEMP_PATH_CREDS` |+| `DATABRICKS_COMPUTE_CLUSTER_POLICIES_GET_PERMISSION_LEVELS` | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_GET_PERM_LEVELS` |+| `DATABRICKS_COMPUTE_CLUSTER_POLICIES_GET_PERMISSIONS` | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_GET_PERMS` |+| `DATABRICKS_COMPUTE_CLUSTER_POLICIES_SET_PERMISSIONS` | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_SET_PERMS` |+| `DATABRICKS_COMPUTE_CLUSTER_POLICIES_UPDATE_PERMISSIONS` | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_UPDATE_PERMS` |+| `DATABRICKS_COMPUTE_INSTANCE_POOLS_GET_PERMISSION_LEVELS` | `DATABRICKS_COMPUTE_INSTANCE_POOLS_GET_PERM_LEVELS` |+| `DATABRICKS_COMPUTE_INSTANCE_POOLS_UPDATE_PERMISSIONS` | `DATABRICKS_COMPUTE_INSTANCE_POOLS_UPDATE_PERMS` |+| `DATABRICKS_COMPUTE_POLICY_COMPLIANCE_FOR_CLUSTERS_ENFORCE_COMPLIANCE` | `DATABRICKS_COMPUTE_POLICY_COMPL_FOR_CLUSTERS_ENFORCE_COMPL` |+| `DATABRICKS_COMPUTE_POLICY_COMPLIANCE_FOR_CLUSTERS_GET_COMPLIANCE` | `DATABRICKS_COMPUTE_POLICY_COMPL_FOR_CLUSTERS_GET_COMPL` |+| `DATABRICKS_DASHBOARDS_GENIE_DELETE_CONVERSATION_MESSAGE` | `DATABRICKS_DASHBOARDS_GENIE_DELETE_CONV_MESSAGE` |+| `DATABRICKS_DASHBOARDS_GENIE_EXECUTE_MESSAGE_ATTACHMENT_QUERY` | `DATABRICKS_DASHBOARDS_GENIE_EXECUTE_MESSAGE_ATTACH_QUERY` |+| `DATABRICKS_DASHBOARDS_GENIE_GET_MESSAGE_ATTACHMENT_QUERY_RESULT` | `DATABRICKS_DASHBOARDS_GENIE_GET_MESSAGE_ATTACH_QUERY_RESULT` |+| `DATABRICKS_DASHBOARDS_GENIE_GET_MESSAGE_QUERY_RESULT_BY_ATTACHMENT` | `DATABRICKS_DASHBOARDS_GENIE_GET_MESSAGE_QUERY_RESULT_ATTACH` |+| `DATABRICKS_DASHBOARDS_GENIE_LIST_CONVERSATION_MESSAGES` | `DATABRICKS_DASHBOARDS_GENIE_LIST_CONV_MESSAGES` |+| `DATABRICKS_DASHBOARDS_LAKEVIEW_EMBEDDED_GET_PUBLISHED_DASHBOARD_TOKEN_INFO` | `DATABRICKS_DASHBOARDS_LAKEVIEW_EMBEDDED_GET_PUBLISHED_DASH` |+| `DATABRICKS_DATABASE_DATABASE_GENERATE_DATABASE_CREDENTIAL` | `DATABRICKS_DATABASE_DATABASE_GENERATE_DATABASE_CRED` |+| `DATABRICKS_IAM_PERMISSION_MIGRATION_MIGRATE_PERMISSIONS` | `DATABRICKS_IAM_PERM_MIGRATION_MIGRATE_PERMS` |+| `DATABRICKS_IAMV2_WORKSPACE_IAM_V2_GET_WORKSPACE_ACCESS_DETAIL_LOCAL` | `DATABRICKS_IAMV2_WORKSPACE_IAM_V2_GET_WORKSPACE_ACCESS` |+| `DATABRICKS_JOB_PERMISSION_LEVELS_GETPERMISSIONLEVELS` | `DATABRICKS_JOB_PERM_LEVELS_GETPERMISSIONLEVELS` |+| `DATABRICKS_JOBS_POLICY_COMPLIANCE_FOR_JOBS_GET_COMPLIANCE` | `DATABRICKS_JOBS_POLICY_COMPL_FOR_JOBS_GET_COMPL` |+| `DATABRICKS_MARKETPLACE_CONSUMER_INSTALLATIONS_CREATE` | `DATABRICKS_MKTPLACE_CONSUMER_INSTALLATIONS_CREATE` |+| `DATABRICKS_MARKETPLACE_CONSUMER_INSTALLATIONS_DELETE` | `DATABRICKS_MKTPLACE_CONSUMER_INSTALLATIONS_DELETE` |+| `DATABRICKS_MARKETPLACE_CONSUMER_INSTALLATIONS_UPDATE` | `DATABRICKS_MKTPLACE_CONSUMER_INSTALLATIONS_UPDATE` |+| `DATABRICKS_MARKETPLACE_CONSUMER_LISTINGS_BATCH_GET` | `DATABRICKS_MKTPLACE_CONSUMER_LISTINGS_BATCH_GET` |+| `DATABRICKS_MARKETPLACE_CONSUMER_PERSONALIZATION_REQUESTS_GET` | `DATABRICKS_MKTPLACE_CONSUMER_PERSONALIZATION_REQUESTS_GET` |+| `DATABRICKS_MARKETPLACE_CONSUMER_PROVIDERS_BATCH_GET` | `DATABRICKS_MKTPLACE_CONSUMER_PROVIDERS_BATCH_GET` |+| `DATABRICKS_MARKETPLACE_PROVIDER_EXCHANGES_DELETE_LISTING_FROM_EXCHANGE` | `DATABRICKS_MKTPLACE_PROVIDER_EXCHANGES_DELETE_LISTING` |+| `DATABRICKS_MARKETPLACE_PROVIDER_PROVIDER_ANALYTICS_DASHBOARDS_CREATE` | `DATABRICKS_MKTPLACE_PROVIDER_ANALYTICS_DASHBOARDS_CREATE` |+| `DATABRICKS_MARKETPLACE_PROVIDER_PROVIDER_ANALYTICS_DASHBOARDS_GET` | `DATABRICKS_MKTPLACE_PROVIDER_ANALYTICS_DASHBOARDS_GET` |+| `DATABRICKS_MARKETPLACE_PROVIDER_PROVIDER_ANALYTICS_DASHBOARDS_GET_LATEST_VERSION` | `DATABRICKS_MKTPLACE_PROVIDER_ANALYTICS_DASH_GET_LATEST` |+| `DATABRICKS_ML_FEATURE_ENGINEERING_DELETE_KAFKA_CONFIG` | `DATABRICKS_ML_FEATURE_ENG_DELETE_KAFKA_CONFIG` |+| `DATABRICKS_ML_MATERIALIZED_FEATURES_DELETE_FEATURE_TAG` | `DATABRICKS_ML_MAT_FEATURES_DELETE_FEATURE_TAG` |+| `DATABRICKS_ML_MATERIALIZED_FEATURES_GET_FEATURE_TAG` | `DATABRICKS_ML_MAT_FEATURES_GET_FEATURE_TAG` |+| `DATABRICKS_ML_MATERIALIZED_FEATURES_UPDATE_FEATURE_TAG` | `DATABRICKS_ML_MAT_FEATURES_UPDATE_FEATURE_TAG` |+| `DATABRICKS_ML_MODEL_REGISTRY_GET_PERMISSION_LEVELS` | `DATABRICKS_ML_MODEL_REGISTRY_GET_PERM_LEVELS` |+| `DATABRICKS_PIPELINES_PIPELINES_GET_PERMISSION_LEVELS` | `DATABRICKS_PIPELINES_PIPELINES_GET_PERM_LEVELS` |+| `DATABRICKS_QUALITYMONITORV2_QUALITY_MONITOR_V2_CREATE_QUALITY_MONITOR` | `DATABRICKS_QUALITYMONITORV2_QUALITY_MONITOR_V2_CREATE` |+| `DATABRICKS_SERVING_SERVING_ENDPOINTS_CREATE_PROVISIONED_THROUGHPUT_ENDPOINT` | `DATABRICKS_SERVING_SERVING_ENDPOINTS_CREATE_PROV_THPUT` |+| `DATABRICKS_SERVING_SERVING_ENDPOINTS_GET_PERMISSION_LEVELS` | `DATABRICKS_SERVING_SERVING_ENDPOINTS_GET_PERM_LEVELS` |+| `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_ACCESS_POLICY_DELETE` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_ACCESS_POLICY_DELETE` |+| `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_ACCESS_POLICY_GET` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_ACCESS_POLICY_GET` |+| `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_ACCESS_POLICY_UPDATE` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_ACCESS_POLICY_UPDATE` |+| `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_APPROVED_DOMAINS_DELETE` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_DOMAINS_DELETE` |+| `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_APPROVED_DOMAINS_GET` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_APPROVED_DOMAINS_GET` |+| `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_APPROVED_DOMAINS_UPDATE` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_DOMAINS_UPDATE` |+| `DATABRICKS_SETTINGS_COMPLIANCE_SECURITY_PROFILE_GET` | `DATABRICKS_SETTINGS_COMPL_SECURITY_PROFILE_GET` |+| `DATABRICKS_SETTINGS_DASHBOARD_EMAIL_SUBSCRIPTIONS_DELETE` | `DATABRICKS_SETTINGS_DASH_EMAIL_SUBS_DELETE` |+| `DATABRICKS_SETTINGS_DASHBOARD_EMAIL_SUBSCRIPTIONS_GET` | `DATABRICKS_SETTINGS_DASH_EMAIL_SUBS_GET` |+| `DATABRICKS_SETTINGS_DASHBOARD_EMAIL_SUBSCRIPTIONS_UPDATE` | `DATABRICKS_SETTINGS_DASH_EMAIL_SUBS_UPDATE` |+| `DATABRICKS_SETTINGS_ENABLE_EXPORT_NOTEBOOK_GET_ENABLE_EXPORT_NOTEBOOK` | `DATABRICKS_SETTINGS_ENABLE_EXPORT_NOTEBOOK_GET_ENABLE` |+| `DATABRICKS_SETTINGS_ENABLE_EXPORT_NOTEBOOK_PATCH_ENABLE_EXPORT_NOTEBOOK` | `DATABRICKS_SETTINGS_ENABLE_EXPORT_NOTEBOOK_PATCH_ENABLE` |+| `DATABRICKS_SETTINGS_ENABLE_NOTEBOOK_TABLE_CLIPBOARD_GET_ENABLE_NOTEBOOK_TABLE_CLIPBOARD` | `DATABRICKS_SETTINGS_ENABLE_NOTEBOOK_TABLE_CLIPBOARD_GET` |+| `DATABRICKS_SETTINGS_ENABLE_NOTEBOOK_TABLE_CLIPBOARD_PATCH_ENABLE_NOTEBOOK_TABLE_CLIPBOARD` | `DATABRICKS_SETTINGS_ENABLE_NOTEBOOK_TABLE_CLIPBOARD_PATCH` |+| `DATABRICKS_SETTINGS_ENABLE_RESULTS_DOWNLOADING_GET_ENABLE_RESULTS_DOWNLOADING` | `DATABRICKS_SETTINGS_ENABLE_RESULTS_DOWNLOADING_GET_ENABLE` |+| `DATABRICKS_SETTINGS_LLM_PROXY_PARTNER_POWERED_WORKSPACE_DELETE` | `DATABRICKS_SETTINGS_LLM_PROXY_PARTNER_WORKSPACE_DELETE` |+| `DATABRICKS_SETTINGS_LLM_PROXY_PARTNER_POWERED_WORKSPACE_UPDATE` | `DATABRICKS_SETTINGS_LLM_PROXY_PARTNER_WORKSPACE_UPDATE` |+| `DATABRICKS_SETTINGS_NOTIFICATION_DESTINATIONS_CREATE` | `DATABRICKS_SETTINGS_NOTIF_DESTS_CREATE` |+| `DATABRICKS_SETTINGS_NOTIFICATION_DESTINATIONS_DELETE` | `DATABRICKS_SETTINGS_NOTIF_DESTS_DELETE` |+| `DATABRICKS_SETTINGS_NOTIFICATION_DESTINATIONS_UPDATE` | `DATABRICKS_SETTINGS_NOTIF_DESTS_UPDATE` |+| `DATABRICKS_SETTINGS_TOKEN_MANAGEMENT_GET_PERMISSION_LEVELS` | `DATABRICKS_SETTINGS_TOKEN_MGMT_GET_PERM_LEVELS` |+| `DATABRICKS_SETTINGS_TOKEN_MANAGEMENT_GET_PERMISSIONS` | `DATABRICKS_SETTINGS_TOKEN_MGMT_GET_PERMS` |+| `DATABRICKS_SETTINGS_TOKEN_MANAGEMENT_SET_PERMISSIONS` | `DATABRICKS_SETTINGS_TOKEN_MGMT_SET_PERMS` |+| `DATABRICKS_SETTINGS_TOKEN_MANAGEMENT_UPDATE_PERMISSIONS` | `DATABRICKS_SETTINGS_TOKEN_MGMT_UPDATE_PERMS` |+| `DATABRICKS_SETTINGSV2_WORKSPACE_SETTINGS_V2_GET_PUBLIC_WORKSPACE_SETTING` | `DATABRICKS_SETTINGSV2_WORKSPACE_SETTINGS_V2_GET_PUBLIC` |+| `DATABRICKS_SQL_STATEMENT_EXECUTION_CANCEL_EXECUTION` | `DATABRICKS_SQL_STATEMENT_EXEC_CANCEL_EXEC` |+| `DATABRICKS_VECTORSEARCH_VECTOR_SEARCH_ENDPOINTS_CREATE_ENDPOINT` | `DATABRICKS_VECTORSEARCH_VECTOR_SEARCH_ENDPOINTS_CREATE` |+| `DATABRICKS_VECTORSEARCH_VECTOR_SEARCH_INDEXES_UPSERT_DATA_VECTOR_INDEX` | `DATABRICKS_VECTORSEARCH_VECTOR_SEARCH_INDEXES_UPSERT_DATA` |+| `DEPLOYHQ_DELETE_PROJECTS_PROJECT_BUILD_CACHE_FILES_IDENTIFIER` | `DEPLOYHQ_DELETE_PROJECTS_PROJECT_BUILD_CACHE_FILES` |+| `DROPBOX_SIGN_EDIT_AND_RESEND_EMBEDDED_SIGNATURE_REQUEST_WITH_TEMPLATE` | `DROPBOX_SIGN_EDIT_RESEND_EMBEDDED_SIGNATURE_REQUEST_TEMPLATE` |+| `GITHUB_CREATE_OR_UPDATE_CUSTOM_PROPERTIES_FOR_AN_ORGANIZATION` | `GITHUB_CREATE_OR_UPDATE_CUSTOM_PROPERTIES_FOR_AN_ORG` |+| ... and 100+ more |++</Accordion>+</Accordions>++## Migration++If you're referencing any affected tool enums by their old names, update to the new shortened names.diff --git a/fumadocs/content/changelog/01-12-26-tool-router-improvements.mdx b/fumadocs/content/changelog/01-12-26-tool-router-improvements.mdxnew file mode 100644index 000000000..f131ad182--- /dev/null+++ b/fumadocs/content/changelog/01-12-26-tool-router-improvements.mdx@@ -0,0 +1,129 @@+---+title: "Tool Router Improvements and New Features"+date: "2026-01-12"+---++## Version Information++### TypeScript/JavaScript+- Package: `@composio/core` and provider packages+- Version: `0.3.4` to `0.4.0`++### Python+- Package: `composio-core` and provider packages+- Version: `0.10.4` to `0.10.5`++## New Features++### 1. Wait for Connections Property++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.++**TypeScript:**+```typescript+const session = await composio.toolRouter.create(userId, {+ manageConnections: {+ enable: true,+ callbackUrl: 'https://example.com/callback',+ waitForConnections: true // NEW+ }+});+```++**Python:**+```python+session = tool_router.create(+ user_id="user_123",+ manage_connections={+ "enable": True,+ "callback_url": "https://example.com/callback",+ "wait_for_connections": True # NEW+ }+)+```++### 2. Session-Specific Modifier Types++Introduced new modifier types for better session-based tool execution: `SessionExecuteMetaModifiers` and `SessionMetaToolOptions`.++**TypeScript:**+```typescript+const tools = await session.tools({+ modifySchema: ({ toolSlug, toolkitSlug, schema }) => schema,+ beforeExecute: ({ toolSlug, toolkitSlug, sessionId, params }) => params,+ afterExecute: ({ toolSlug, toolkitSlug, sessionId, result }) => result+});+```++**Python:**+```python+from composio.core.models import before_execute_meta, after_execute_meta++@before_execute_meta+def before_modifier(tool, toolkit, session_id, params):+ return params++@after_execute_meta+def after_modifier(tool, toolkit, session_id, response):+ return response++tools = session.tools(modifiers=[before_modifier, after_modifier])+```++### 3. Dedicated Method for Tool Router Meta Tools++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.++**TypeScript:**+```typescript+const metaTools = await composio.tools.getRawToolRouterMetaTools('session_123', {+ modifySchema: ({ toolSlug, toolkitSlug, schema }) => {+ // Customize schema+ return schema;+ }+});+```++**Python:**+```python+meta_tools = tools_model.get_raw_tool_router_meta_tools(+ session_id="session_123",+ modifiers=[schema_modifier]+)+```++## Internal Improvements++### 1. Performance Optimization++Eliminated unnecessary tool fetching during tool router execution, resulting in faster tool execution with fewer API calls.++### 2. Improved Architecture++Tool router sessions now fetch tools directly from the session API endpoint instead of using tool slugs, providing better consistency and reliability.++### 3. Simplified Implementation++Removed redundant tool schema fetching in execution paths, using a hardcoded 'composio' toolkit slug for meta tools.++## Backward Compatibility++This release is fully backward compatible:++- All existing code continues to work without modifications+- New properties are optional with sensible defaults+- New modifier types can be adopted incrementally+- Internal changes have no impact on public APIs+- No migration required++## Impact Summary++| Change | Runtime Breaking | TypeScript Breaking | Migration Required |+|--------|------------------|---------------------|-------------------|+| `wait_for_connections` property | No | No | No |+| Session-specific modifiers | No | No | No |+| `getRawToolRouterMetaTools` method | No | No | No |+| Tool router uses session API | No | No | No |+| Optimized tool execution | No | No | No |++All changes follow semantic versioning principles and maintain full backward compatibility.diff --git a/fumadocs/content/changelog/12-30-25-proxy-binary-data.mdx b/fumadocs/content/changelog/12-30-25-proxy-binary-data.mdxnew file mode 100644index 000000000..c6a0b7230--- /dev/null+++ b/fumadocs/content/changelog/12-30-25-proxy-binary-data.mdx@@ -0,0 +1,91 @@+---+title: "Binary Data Support for Proxy Execute"+date: "2025-12-30"+---++The `/api/v3/tools/execute/proxy` endpoint now supports binary data for both file uploads and downloads.++### File Uploads (`binary_body`)++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.++#### Upload File via URL++```bash+curl --location 'https://backend.composio.dev/api/v3/tools/execute/proxy' \+ --header 'accept: application/json' \+ --header 'x-api-key: <YOUR_API_KEY>' \+ --header 'Content-Type: application/json' \+ --data '{+ "endpoint": "/upload-endpoint",+ "method": "POST",+ "connected_account_id": "<CONNECTED_ACCOUNT_ID>",+ "binary_body": {+ "url": "{URL_TO_THE_FILE}"+ }+ }'+```++#### Upload File via Base64 Content++Supported up to 4MB file size.++```bash+curl --location 'https://backend.composio.dev/api/v3/tools/execute/proxy' \+ --header 'accept: application/json' \+ --header 'x-api-key: <YOUR_API_KEY>' \+ --header 'Content-Type: application/json' \+ --data '{+ "endpoint": "/upload-endpoint",+ "method": "POST",+ "connected_account_id": "<CONNECTED_ACCOUNT_ID>",+ "binary_body": {+ "base64": "JVBERi0xLjQKJ...<base64_data>...",+ "content_type": "application/pdf"+ }+ }'+```++### File Downloads (`binary_data`)++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.++#### File Download Request++```bash+curl --location 'https://backend.composio.dev/api/v3/tools/execute/proxy' \+ --header 'accept: application/json' \+ --header 'x-api-key: <YOUR_API_KEY>' \+ --header 'Content-Type: application/json' \+ --data '{+ "endpoint": "{YOUR_ENDPOINT}",+ "method": "GET",+ "connected_account_id": "{YOUR_CONNECTED_ACCOUNT_ID}"+ }'+```++#### File Download Response++```json+{+ "data": {},+ "binary_data": {+ "url": "url to the file",+ "content_type": "content type of the file",+ "size": "size of the file",+ "expires_at": "expires at of the file"+ },+ "status": "status code of the response",+ "headers": "headers of the response"+}+```++### Summary++| Feature | Field | Description |+|---------|-------|-------------|+| File Upload via URL | `binary_body.url` | Provide a URL pointing to the file to upload |+| File Upload via Base64 | `binary_body.base64` + `binary_body.content_type` | Provide base64-encoded content (up to 4MB) |+| File Download | `binary_data` in response | Receive a signed URL to download binary responses |++We'd love your feedback on the new proxy execute capabilities. If anything feels unclear or you have suggestions for improvement, please reach out.diff --git a/fumadocs/content/changelog/12-30-25.mdx b/fumadocs/content/changelog/12-30-25.mdxnew file mode 100644index 000000000..fd8ae7365--- /dev/null+++ b/fumadocs/content/changelog/12-30-25.mdx@@ -0,0 +1,151 @@+---+title: "Webhook Payload V3 - Lookahead Announcement"+date: "2025-12-30"+---++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.++## What's Changing?++### New Webhook Structure++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.++#### Headers+A new header will identify the webhook version:+```+x-composio-webhook-version: V3+```++#### Payload Structure+The payload structure is being reorganized to separate Composio metadata from trigger data:++**Before (V2):**+```json+{+ "log_id": "log_TpxVOLXYnwXZ",+ "timestamp": "2025-12-23T13:06:07.695Z",+ "type": "gmail_new_gmail_message",+ "data": {+ "connection_id": "a1b2c3d4-5e6f-7a8b-9c0d-1e2f3a4b5c6d",+ "connection_nano_id": "ca_xYz9AbCdEfGh",+ "trigger_nano_id": "ti_JZFoTyYKbzhB",+ "trigger_id": "7f8e9d0c-1b2a-3c4d-5e6f-7a8b9c0d1e2f",+ "user_id": "usr-demo-12a3b4c5...",+ // ... actual trigger data mixed with metadata+ }+}+```++**After (V3):**+```json+{+ "id": "msg_a1b2c3d4-5e6f-7a8b-9c0d-1e2f3a4b5c6d",+ "timestamp": "2025-12-23T13:06:07.695Z",+ "type": "composio.trigger.message",+ "metadata": {+ "log_id": "log_TpxVOLXYnwXZ",+ "trigger_slug": "GMAIL_NEW_GMAIL_MESSAGE",+ "auth_config_id": "ac_aCYTppZ5RsRc",+ "connected_account_id": "ca_cATYssZ5RrSc",+ "trigger_id": "ti_JZFoTyYKbzhB",+ "user_id": "pg-test-86c9fc84..."+ },+ "data": {+ // Clean trigger data without Composio metadata+ }+}+```++### Key Improvements++1. **Metadata Separation**: Composio-specific fields (connection IDs, trigger IDs, user IDs) are now in a dedicated `metadata` object+2. **Clean Data**: The `data` field now contains only the actual trigger payload without infrastructure metadata+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`+4. **Trigger Slug in Metadata**: The trigger slug (e.g., `GMAIL_NEW_GMAIL_MESSAGE`) is now available in `metadata.trigger_slug` for easy identification+5. **Standards Compliance**: Follows Standard Webhooks specification for better interoperability+6. **Consistent Structure**: Same payload structure for both webhooks and Pusher channels++## Migration Guide++### Updating Your Webhook Handlers++If you're accessing Composio metadata fields, update your code:++```python+# Before (V2)+trigger_type = payload["type"] # "gmail_new_gmail_message"+connection_id = payload["data"]["connection_id"]+trigger_id = payload["data"]["trigger_id"]+message_text = payload["data"]["message_text"]++# After (V3)+trigger_type = payload["type"] # "composio.trigger.message"+trigger_slug = payload["metadata"]["trigger_slug"] # "GMAIL_NEW_GMAIL_MESSAGE"+connection_id = payload["metadata"]["connected_account_id"]+trigger_id = payload["metadata"]["trigger_id"]+message_text = payload["data"]["message_text"]+```++```typescript+// Before (V2)+const triggerSlug = payload.type; // "gmail_new_gmail_message"+const connectionId = payload.data.connection_id;+const triggerId = payload.data.trigger_id;+const messageText = payload.data.message_text;++// After (V3)+const webhookType = payload.type; // "composio.trigger.message"+const triggerSlug = payload.metadata.trigger_slug; // "GMAIL_NEW_GMAIL_MESSAGE"+const connectionId = payload.metadata.connected_account_id;+const triggerId = payload.metadata.trigger_id;+const messageText = payload.data.message_text;+```++### Checking Webhook Version++You can detect the webhook version from headers:++```python+webhook_version = headers.get("x-composio-webhook-version", "V2")+if webhook_version == "V3":+ # Use new structure+ metadata = payload["metadata"]+else:+ # Use old structure+ metadata = payload["data"]+```++## Rollout Timeline++- **December 2025**: V3 released, opt-in via project settings+- **February 15, 2026**: All new organizations will default to V3+- **Existing organizations**: Continue using V2 by default, can opt-in to V3 anytime++## How to Opt-In++1. Go to your project settings in the Composio dashboard+2. Navigate to the Webhooks section+3. Select "Webhook Payload Version: V3"+4. Update your webhook handlers to use the new structure+5. Test thoroughly before enabling in production++<Callout type="info">+Organizations created **before February 15, 2026** will remain on V2 by default. You can switch to V3 at your convenience.++Organizations created **on or after February 15, 2026** will use V3 by default.+</Callout>++## Benefits++- **Better DX**: Clear separation between metadata and actual trigger data+- **Standards Compliance**: Follows industry-standard webhook specifications+- **Consistency**: Same structure across webhooks and Pusher channels+- **Future-Proof**: Built on established standards for long-term compatibility++## Need Help?++If you have questions about migrating to V3 or need assistance:+- Join our [Discord community](https://discord.gg/composio)+- Check our [documentation](https://docs.composio.dev)+- Contact support at [email protected]diff --git a/fumadocs/content/changelog/12-31-25.mdx b/fumadocs/content/changelog/12-31-25.mdxnew file mode 100644index 000000000..ca1c0f33f--- /dev/null+++ b/fumadocs/content/changelog/12-31-25.mdx@@ -0,0 +1,38 @@+---+title: "Deprecating BEARER_TOKEN auth scheme for 19 toolkits"+date: "2025-12-31"+---++We've **deprecated** the `BEARER_TOKEN` auth scheme for the following **19 toolkits**:++- `Airtable`+- `Discord`+- `Discordbot`+- `Gmail`+- `Google Classroom`+- `Google Search Console`+- `Google Calendar`+- `Google Docs`+- `Google Drive`+- `Google Slides`+- `Google Super`+- `Instagram`+- `Ntfy`+- `Sapling AI`+- `Slack`+- `Slackbot`+- `Tawk To`+- `TikTok`+- `Twitter`++### Recommendation++For these toolkits, we recommend using **alternative auth schemes** (for example, `OAUTH2`, `API_KEY`, or other toolkit-supported schemes) instead of `BEARER_TOKEN`.++### Backward compatibility (explicit)++This change is **fully backward compatible**:++- **Existing** auth configs and connected accounts created with `BEARER_TOKEN` **will continue to function**.+- **Creating new** auth configs and connected accounts with `BEARER_TOKEN` **will continue to work** (e.g., via API/SDK).+- To discourage new usage, `BEARER_TOKEN` auth configs / connected accounts **will not be displayed in the UI** for these toolkits.