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: add changelog entry for API v3.1 tool version defaults
rahul.lingala856d49267f95
diff --git a/docs/content/changelog/04-08-26-v31-api.mdx b/docs/content/changelog/04-08-26-v31-api.mdxnew file mode 100644index 000000000..d82a19de0--- /dev/null+++ b/docs/content/changelog/04-08-26-v31-api.mdx@@ -0,0 +1,55 @@+---+title: "Introducing API v3.1 - Latest Tool Versions by Default"+description: "API v3.1 endpoints now default to the latest toolkit version for tool-related endpoints instead of the legacy pinned version."+date: "2026-04-08"+---++We're rolling out API v3.1 endpoints that change how tool versions are resolved. The key difference: **tool-related endpoints now default to the latest toolkit version** instead of the legacy pinned version (`00000000_00`).++### What Changed++In API v3 (`/api/v3/tools/*`), tool-related endpoints default the `version` parameter to `00000000_00` (the initial pinned version). This means callers must explicitly pass `version: "latest"` or a specific version string to get the most recent tool definitions.++In API v3.1 (`/api/v3.1/tools/*`), the default is flipped: **tool-related endpoints default to the latest toolkit version**. If you're already passing `version: "latest"` in your requests, switching to v3.1 changes nothing for you. If you were relying on the `00000000_00` default, you'll now get the latest version unless you explicitly pin.++**Affected tool endpoints:**++| Endpoint | v3 Default Version | v3.1 Default Version |+|----------|-------------------|---------------------|+| `GET /tools` | `00000000_00` | `latest` |+| `GET /tools/enum` | `00000000_00` | `latest` |+| `GET /tools/{tool_slug}` | `00000000_00` | `latest` |+| `POST /tools/execute/{tool_slug}` | `00000000_00` | `latest` |+| `POST /tools/execute/{tool_slug}/input` | `00000000_00` | `latest` |+| `POST /tools/execute/proxy` | `00000000_00` | `latest` |+| `POST /tools/scopes/required` | `00000000_00` | `latest` |++### All Other Endpoints Are Unchanged++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.++### Migration Guide++**If you're using the Composio SDK:** No action needed. The SDK will adopt v3.1 endpoints in an upcoming release.++**If you're calling the API directly:**++1. Replace `/api/v3/` with `/api/v3.1/` in your tool endpoint URLs+2. If you depend on a specific pinned version, pass `version: "00000000_00"` explicitly+3. If you were already passing `version: "latest"`, you can drop the parameter entirely on v3.1++**Before (v3):**+```bash+curl https://backend.composio.dev/api/v3/tools?toolkit_slug=gmail&toolkit_versions=latest \+ -H "x-api-key: YOUR_KEY"+```++**After (v3.1):**+```bash+curl https://backend.composio.dev/api/v3.1/tools?toolkit_slug=gmail \+ -H "x-api-key: YOUR_KEY"+```++### v3 Is Not Going Away++API v3 endpoints continue to work exactly as before. There is no deprecation timeline. You can migrate to v3.1 at your own pace.