@devries-cameron20 / composio Mirror · read-only / commits / dc3cc6e8e
Fork 0

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 21, 23:30 UTC

docs: note that triggers have no behavior change in v3.1

The version param for triggers already defaults to 'latest' in both v3 and v3.1, so there is no change in triggers behavior. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: rahul.lingala <rahul.lingala@composio.dev>

Zen Agent committed Apr 13, 2026 at 10:59 UTC dc3cc6e8e583444a102376c8648b0a3d7c1d0b22
1 file changed +4
docs/content/changelog/04-08-26-v31-api.mdx
+4
@@ -22,6 +22,10 @@ In API v3.1 (`/api/v3.1/tools/*`), the default is flipped: **tool-related endpoi
22 | `POST /tools/execute/{tool_slug}/input` | `version` (body) | `00000000_00` | `latest` |
23 | `POST /tools/scopes/required` | `version` (body) | `00000000_00` | `latest` |
24
25 +### Triggers Are Unchanged
26 +
27 +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.
28 +
29 ### All Other Endpoints Are Unchanged
30
31 Every 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.