@devries-cameron20 / composio Mirror · read-only / commits / 5d3c7e0e1
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 23:30 UTC

docs(changelog): make link-auth rollout dates explicit + clarify motivation

Pin the phased rollout to Friday, May 1, 2026 (new orgs) and Friday, July 3, 2026 (all remaining orgs) instead of "first week of" phrasing. Rewrite the "Why" section to make the motivation concrete: connections initiated via default (Composio-managed) auth configs are backed by a Composio-owned OAuth application acting on the developer's behalf, and the end user should be given an explicit consent step before that third-party access is granted. Custom auth configs are unaffected because the developer owns the consent experience through their own OAuth app. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Composio committed Apr 24, 2026 at 14:41 UTC 5d3c7e0e1a60bdb945f013b13271e5c9ca414946
1 file changed +8 -6
docs/content/changelog/04-24-26-link-auth-migration.mdx
+8 -6
@@ -1,10 +1,10 @@
1 ---
2 title: "Link Auth Migration for Composio-Managed OAuth Connections"
3 -description: "POST /api/v3/connected_accounts will stop creating Composio-managed OAuth1/OAuth2/DCR_OAUTH connections. Callers must migrate to POST /api/v3/connected_accounts/link. Rollout begins the first week of May 2026 for new organizations."
3 +description: "POST /api/v3/connected_accounts will stop creating Composio-managed OAuth1/OAuth2/DCR_OAUTH connections. Callers must migrate to POST /api/v3/connected_accounts/link. Rollout begins Friday, May 1, 2026 for new organizations."
4 date: "2026-04-24"
5 ---
6
7 -`POST /api/v3/connected_accounts` is being retired for **Composio-managed OAuth connections**. New organizations begin migrating the first week of May 2026, and all remaining organizations follow the first week of July 2026. Once migrated, affected requests receive `400 BadRequest` with a message pointing at the replacement endpoint.
7 +`POST /api/v3/connected_accounts` is being retired for **Composio-managed OAuth connections**. New organizations begin migrating on **Friday, May 1, 2026**, and all remaining organizations follow on **Friday, July 3, 2026**. Once migrated, affected requests receive `400 BadRequest` with a message pointing at the replacement endpoint.
8
9 This does **not** affect custom auth configs (your own OAuth app) or non-OAuth schemes (API key, bearer token, basic auth, etc.) — those continue to work on `POST /api/v3/connected_accounts` unchanged. Only the specific combination of **Composio-managed auth config + redirectable OAuth scheme** (OAuth1, OAuth2, DCR_OAUTH) is moving.
10
@@ -13,8 +13,8 @@ This does **not** affect custom auth configs (your own OAuth app) or non-OAuth s
13
14 If your integration calls `POST /api/v3/connected_accounts` for a Composio-managed OAuth1, OAuth2, or DCR_OAUTH auth config, it will start returning `400 BadRequest` on the dates below. Migrate to `POST /api/v3/connected_accounts/link` before your organization's cutover.
15
16 -- **First week of May 2026** — organizations created on or after this window are blocked.
17 -- **First week of July 2026** — all remaining organizations are blocked.
16 +- **Friday, May 1, 2026 (00:00 UTC)** — organizations created on or after this timestamp are blocked.
17 +- **Friday, July 3, 2026 (00:00 UTC)** — all remaining organizations are blocked.
18 </Callout>
19
20 ### What's Changing
@@ -28,7 +28,9 @@ If your integration calls `POST /api/v3/connected_accounts` for a Composio-manag
28
29 ### Why
30
31 -The link endpoint is built to make it explicit to the end user that they are authorizing a third-party application, and it produces a consistent redirect URL for every redirectable scheme. Concentrating Composio-managed OAuth flows on `/link` removes the DX ambiguity of a single endpoint that either returns a redirect URL or creates a fully-initialized connection depending on inputs.
31 +When a connection is initiated through a default (Composio-managed) auth config, a Composio-owned OAuth application is acting on behalf of your integration. We want the end user to 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. That acknowledgement is enforced by the `/link` flow, which routes the user through a consent screen before the connection is created. The legacy `POST /api/v3/connected_accounts` path allowed that step to be bypassed when credentials were passed in directly, which this change closes.
32 +
33 +Custom auth configs are unaffected because they are backed by your own OAuth application — the consent screen is served by your app, so you already own that experience. This change is scoped specifically to default auth configs on redirectable schemes, where the third-party relationship is with Composio rather than with the developer.
34
35 ### Migration
36
@@ -74,6 +76,6 @@ Requests that hit the retired combination receive:
76
77 ### What to Do
78
77 -- **If you use Composio-managed OAuth auth configs** (OAuth1, OAuth2, or DCR_OAUTH) via `POST /api/v3/connected_accounts`: switch to `POST /api/v3/connected_accounts/link` before your org's cutover date.
79 +- **If you use Composio-managed OAuth auth configs** (OAuth1, OAuth2, or DCR_OAUTH) via `POST /api/v3/connected_accounts`: switch to `POST /api/v3/connected_accounts/link` before your org's cutover — **Friday, May 1, 2026** for organizations created on or after that date, **Friday, July 3, 2026** for all others.
80 - **If you already use `/link`**: no action required.
81 - **If you use custom OAuth apps (your own `client_id` / `client_secret`) or non-OAuth auth (API key, bearer, etc.)**: no action required — the legacy endpoint continues to serve those cases.