Composio API
/api/v1/* version retirement
Stopped workingSubscribe to Composio APIShare
On June 4, 2026, Composio API removed legacy endpoints including /api/v1/*. Calls targeting these routes now fail and return 410 instead of completing normally.
Calls it hits
/api/v1/*
What to use instead of these calls
Use the v3 or v3.1 endpoints instead.
In Composio API's words
The legacy v1 and v2 endpoints, deprecated last year, have now been removed. Any calls to /v1 or v2 endpoints now return 410
Facts
- API
- Composio API
backend.composio.dev - Kind
- Version retirement
- 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 /api/v1/* 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/v2/*Version retirement Stopped working -
POST /api/v3/tools/execute/proxyEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.