Changelog & Updates
Tracking changes, deprecations, and migrations for Composio
This page tracks important updates, new features, deprecations, and migration information for the Composio platform, APIs, and SDKs. Check back regularly to stay informed about the latest changes.
Updates
Keep up-to-date with the latest releases, deprecations, and announcements.
[2025-04-22] Deprecation: V1/V2 Projects and API Keys APIs
The V1/V2 Projects and API Keys APIs are now deprecated as of April 22nd, 2025. They will be fully removed by June 22nd, 2025. These APIs have been replaced by the improved V3 Organization API structure.
Endpoints deprecated:
- V1 Projects APIs:
- V1 API Keys APIs:
Please update your applications to use the new V3 Organization API to ensure continued functionality.
Migration Table
Below is a mapping between deprecated V1/V2 endpoints and their V3 replacements:
[2025-04-21] Deprecation: V1 Initiate Connection API
The /v1/connectedAccounts
endpoint, used to start the authentication flow for connecting user accounts is deprecated as of April 21st, 2025. It will be fully removed by April 28th, 2025.
The recommended endpoint to use is /v2/connectedAccounts/initiateConnection
. Please update your applications to use the V2 endpoint immediately to avoid service interruption.
[2025-04-16] Release: Experimental V3 Base SDKs
We have released experimental base SDKs for Python and Node.js that wrap the new V3 API (currently in alpha). These SDKs provide foundational access to the V3 API endpoints.
These are foundational SDKs. More developer-friendly core SDKs and framework-specific integrations (like Langchain, OpenAI Assistants) built on V3 are coming soon! Documentation for these SDKs will follow shortly.
[2025-04-10] Deprecation: V1/V2 Log APIs
The V1/V2 Action Log APIs (endpoints for fetching historical action execution logs) are now deprecated as of April 10th, 2025. They have been replaced by the enhanced V3 Logs API.
Endpoints deprecated:
- V1 Action Log APIs:
/v1/logs
- V2 Action Log API:
/v2/actions/logs/all/
Please update your applications to use the new V3 Logs API to leverage improved logging, tracing capabilities, and ensure continued functionality.
Migration Resources
To help with migrations mentioned in the updates above, refer to these resources:
API Migration Resources
- V3 Organization API Reference - For Projects and API Keys APIs migration
- V2 Initiate Connection API Reference - For V1 Connection API migration
- V3 Logs API Reference - For V1/V2 Logs APIs migration
Support Channels
- Discord Community - Join our community for real-time assistance
- Technical Support - Email our team for migration assistance
- GitHub Issues - Report issues or request features
V3 API Migration Overview
This section provides high-level context about the ongoing migration to Composio’s V3 API infrastructure. Specific V3-related releases or deprecations will be announced in the Updates section above.
Why V3?
V3 represents a significant improvement over previous versions. It offers:
- Enhanced Performance: Faster response times and improved stability, especially for tool calls and triggers.
- More Intuitive: Streamlined interfaces for easier integration.
- Greater Robustness: Significantly improved error handling, suggestions, and validation.
- Simpler Developer Experience: Incorporates user feedback to make the API more user-friendly.
V3 Terminology Changes
As part of V3, we are standardizing our terminology. Please familiarize yourself with these changes:
Future V3 documentation and migration guides will use these new terms.
V1/V2 API Support
We will continue supporting V1/V2 APIs and their corresponding SDKs for the foreseeable future. Existing integrations will continue to work, and we will provide ample notice (minimum two months) before any V1/V2 deprecations occur.
General Rollout Plan for V3
Our V3 rollout is phased to ensure a smooth transition:
- Frontend Implementation: Our dashboard (
app.composio.dev
) is already running on V3 APIs. - Beta API Access: The V3 API will be available for beta users soon.
- Beta SDK Release: Foundational V3 SDKs are now available (see Updates feed). Core and framework-specific SDKs will follow.
- Stable SDK Release (LSE): Once stable, V3 SDKs become primary.
- V1/V2 Deprecation: Deprecation timeline (min. 2 months notice) announced after V3 SDK LSE.
We welcome feedback on the V3 changes: GitHub RFC Issue #1523
V3 Resources
- V3 API Reference
- Migration guides (Coming soon)
- Code examples (Coming soon)
- Migration support channel (Coming soon)
- Contact support via Discord or email