API V3 Migration | Composio

This document serves as a running changelog for Composio’s V3 API upgrade. We track all changes to Composio’s V3 API and SDK, including migration guides, rollout schedules, deprecations, and more.

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: Streamlines interfaces for easier integration.
Greater Robustness: Significantly improved error handling, suggestions and validation.
Simpler Developer Experience: Takes into account the feedback from our users and makes the API more user-friendly.

On top of this, we implemented a major change in nomenclature across the API (Coming soon in the SDK). The table below outlines the terminology changes implemented in the V3 API.

Previous Term	New Term (V3)	Description
App	Toolkit	A collection of LLM-callable tools grouped together for a specific domain or purpose
Action	Tool	A function that can be directly called by an LLM to perform a specific task
Integration	Auth Config	Authentication and configuration settings for a toolkit’s external service connections
Connection	Connected Account	User’s authenticated instance of an external service with active credentials
Entity	User	Individual account with permissions and access to the platform
Trigger	Trigger Types	The available triggers for a user on a specific toolkit
Trigger Metadata	Trigger Instance	Specific configuration and settings for a deployed trigger in your workflow

When migrating your code from previous versions to V3, update your references to match this new terminology. Migration guides and code examples will use these new terms exclusively.

Nothing Changes for you today!

We will be supporting V1/V2 APIs and corresponding SDKs for the foreseeable future, and they will still work in production and have full backwards compatability with new api surface.

Rollout plan

Frontend Implementation - As of right now, app.composio.dev is running on V3 APIs. This phase allows us to gather information about performance and see how the api works in a controlled environment.
Beta Access - We will make the V3 API available for beta users and testers in the coming week.
SDK Release - We will release Beta SDKs revamped for the new API once the V3 API stabilizes.
LSE Release - We will work towards stabilizing the new SDKs that power V3 APIs and get them to a stable release - at which time they will become our primary sdks. we will still be supporting the old sdks at this time
Deprecations - We will deprecate the old APIs and SDKs after the LSE release, with two months of notice before finally discontinuing them.

The rollout plan may change based on feedback and testing results.

We have opened an issue as an RFC for comment on changes here: https://github.com/ComposioHQ/composio/issues/1523

Resources

V3 API references (Coming soon)
Migration guides (Coming soon)
Code examples (Coming soon)
Migration support channel (Coming soon)
Contact support (Coming soon)