Composio API
POST /api/v3/tools/execute/proxy endpoint removal
Stopped workingSubscribe to Composio APIShare
On June 4, 2026, the POST /api/v3/tools/execute/proxy endpoint stopped working. Calls made to this route fail because proxy execute is disabled on the v3 API. Developers making requests to this path must switch away from the disabled endpoint to avoid failures.
Calls it hits
POST /api/v3/tools/execute/proxy
What to use instead of these calls
Call POST /api/v3.1/tools/execute/proxy or update your SDK.
In Composio API's words
Proxy Execute is disabled on v3 api, please use v3.1 or update your sdks.
Facts
- API
- Composio API
backend.composio.dev - Kind
- Endpoint removal
- Announced
- June 4, 2026
- Takes effect
- June 4, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Composio API's own pages
Questions
When does this change take effect?
Calls to POST /api/v3/tools/execute/proxy on Composio API stopped working on June 4, 2026.
What happens to calls after June 4, 2026?
They have failed since June 4, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Composio API 3
-
GET /api/v3/toolkitsParameter removal Stopped working -
/api/v1/*Version retirement Stopped working -
/api/v2/*Version retirement Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.