Skip to main content
composio.connected_accounts.initiate() (Python) and composio.connectedAccounts.initiate() (TypeScript) wrap POST /api/v3/connected_accounts. That endpoint is being retired for Composio-managed auth configs on redirectable OAuth schemes (OAuth1, OAuth2, DCR_OAUTH):
  • 2026-05-08, 00:00 UTC — organizations created on or after this date are blocked.
  • 2026-07-03, 00:00 UTC — all remaining organizations are blocked.
After your org’s cutover, calling initiate() for the affected combination raises ComposioLegacyConnectedAccountsEndpointRetiredError (TS) / composio.exceptions.ComposioLegacyConnectedAccountsEndpointRetiredError (Python). The replacement is link() — same return shape, same redirectUrl / redirect_url, same waitForConnection() / wait_for_connection() helper.
Who this affects: developers using a Composio-managed (default) auth config on OAuth1, OAuth2, or DCR_OAUTH. If you brought your own OAuth client credentials (custom auth config) or use a non-OAuth scheme (API key, bearer, basic), your initiate() calls keep working — no migration needed.

Why

When a connection is initiated through a default (Composio-managed) auth config, a Composio-owned OAuth application is acting on behalf of your integration. The end user should explicitly understand and acknowledge, at the moment of connection, that they are granting a third-party application access to their account on the external service. The link() flow enforces that consent step; the legacy initiate() path could bypass it when credentials were passed in directly. Concentrating Composio-managed OAuth on link() aligns the user experience with that consent guarantee.

Migration at a glance

The signatures are the same shape — only the method name changes for the OAuth case.
Before:
After:
callback_url / callbackUrl works the same way on both methods.

What changes between the two methods

How to know which auth config is which

If you maintain a mix of Composio-managed and custom auth configs and aren’t sure which path to take per call, look at the auth config record. The dashboard shows whether each config is “Default (Composio-managed)” or “Custom”. Programmatically, the auth config retrieve response includes an is_composio_managed (Python) / isComposioManaged (TS) boolean. Route the call based on that field:
For most integrations the auth config is hard-coded per integration, so you’ll know up front which path to use and can drop the branching.