@devries-cameron20 / composio Mirror · read-only / commits / 020fdf689
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): push phase-1 cutover to Fri 2026-05-08

Phase 1 (new-org rollout) slips from 2026-05-01 to 2026-05-08 — still the second Friday of May, one week of additional buffer before the first customer orgs see the block. Phase 2 (all remaining orgs) stays on 2026-07-03. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Composio committed Apr 24, 2026 at 17:23 UTC 020fdf689e58773fc73ed617d8a1531d612d242e
1 file changed +4 -4
docs/content/changelog/04-24-26-link-auth-migration.mdx
+4 -4
@@ -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 Friday, May 1, 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 8, 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 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.
7 +`POST /api/v3/connected_accounts` is being retired for **Composio-managed OAuth connections**. New organizations begin migrating on **Friday, May 8, 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,7 +13,7 @@ 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 -- **Friday, May 1, 2026 (00:00 UTC)** — organizations created on or after this timestamp are blocked.
16 +- **Friday, May 8, 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
@@ -76,6 +76,6 @@ Requests that hit the retired combination receive:
76
77 ### What to Do
78
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.
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 8, 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.