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: note that triggers have no behavior change in v3.1
Zen Agentdc3cc6e8e583
diff --git a/docs/content/changelog/04-08-26-v31-api.mdx b/docs/content/changelog/04-08-26-v31-api.mdxindex 5e881e53e..db3dcbd5d 100644--- a/docs/content/changelog/04-08-26-v31-api.mdx+++ b/docs/content/changelog/04-08-26-v31-api.mdx@@ -22,6 +22,10 @@ In API v3.1 (`/api/v3.1/tools/*`), the default is flipped: **tool-related endpoi| `POST /tools/execute/{tool_slug}/input` | `version` (body) | `00000000_00` | `latest` || `POST /tools/scopes/required` | `version` (body) | `00000000_00` | `latest` |+### Triggers Are Unchanged++Trigger endpoints already default the `version` parameter to `latest` in both v3 and v3.1, so there is **no behavior change** for triggers. If you're using triggers, switching to v3.1 requires no changes.+### All Other Endpoints Are UnchangedEvery non-tool endpoint (`/auth_configs`, `/connected_accounts`, `/triggers`, `/toolkits`, etc.) behaves identically between v3 and v3.1. They are served at both `/api/v3/` and `/api/v3.1/` paths with the same request and response contracts.