Skip to content

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

docs: address review — drop errors.mdx Error 600 section + custom-auth-configs callout

Composio21bff478a61d
diff --git a/docs/content/docs/auth-configuration/custom-auth-configs.mdx b/docs/content/docs/auth-configuration/custom-auth-configs.mdx
index 74cac71cd..4231f65ca 100644
--- a/docs/content/docs/auth-configuration/custom-auth-configs.mdx
+++ b/docs/content/docs/auth-configuration/custom-auth-configs.mdx
@@ -98,10 +98,6 @@ Once you have the OAuth credentials, you can add them to the auth config in the
This auth config is now ready to be used in your application!
-<Callout type="info">
-The `initiate()` example below is **safe for custom auth configs**. The `initiate()` retirement announced in the [2026-04-24 changelog](/docs/changelog/2026/04/24) only affects **Composio-managed** auth configs on OAuth1 / OAuth2 / DCR_OAUTH — not the custom OAuth app you just configured here. Custom auth configs continue to work on `initiate()` indefinitely.
-</Callout>
-
<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
<Tab value="Python">
```python
diff --git a/docs/content/docs/auth-configuration/migrating-initiate-to-link.mdx b/docs/content/docs/auth-configuration/migrating-initiate-to-link.mdx
index 1361fb754..25ca94b4f 100644
--- a/docs/content/docs/auth-configuration/migrating-initiate-to-link.mdx
+++ b/docs/content/docs/auth-configuration/migrating-initiate-to-link.mdx
@@ -209,5 +209,4 @@ This is meant as a safety net during migration — the long-term answer is to sw
- [Connected accounts → Multiple accounts](/docs/auth-configuration/connected-accounts#multiple-accounts) — using `link()` for multi-account flows
- [Authenticating tools → Hosted Authentication](/docs/tools-direct/authenticating-tools#hosted-authentication-connect-link) — the canonical `link()` flow
-- [API errors → Error 600](/reference/errors#error-600) — the 400 response shape
- [Changelog: Link Auth Migration](/docs/changelog/2026/04/24) — the announcement
diff --git a/docs/content/reference/errors.mdx b/docs/content/reference/errors.mdx
index ac085754b..802991bfe 100644
--- a/docs/content/reference/errors.mdx
+++ b/docs/content/reference/errors.mdx
@@ -98,38 +98,6 @@ Errors related to trigger subscriptions.
See [Triggers Troubleshooting](/docs/troubleshooting/triggers) for more help.
</Callout>
-## Specific error codes
-
-When the API response includes a numeric `code` in the error object, you can look it up here for a focused explanation and the canonical fix. The `suggested_fix` field on each error response also points back to this section.
-
-### Error 600
-
-`ConnectedAccount_BadRequest`. Returned by `POST /api/v3/connected_accounts` (HTTP 400) when the request is for a **Composio-managed auth config on a redirectable OAuth scheme** (OAuth1, OAuth2, DCR_OAUTH). This combination is being retired on the legacy create endpoint — **2026-05-08** for new organizations and **2026-07-03** for all remaining organizations.
-
-**Example response:**
-
-```json
-{
- "error": {
- "message": "Creating connections on this endpoint for Composio-managed OAuth auth configs is no longer supported. Use POST /api/v3/connected_accounts/link instead.",
- "code": 600,
- "slug": "ConnectedAccount_BadRequest",
- "status": 400,
- "request_id": "...",
- "suggested_fix": "Call POST /api/v3/connected_accounts/link with the same auth_config_id and user_id to get a redirect URL for the end user."
- }
-}
-```
-
-**Fix.** Switch the call to `POST /api/v3/connected_accounts/link`, or use the SDK helper:
-
-- TypeScript: `composio.connectedAccounts.link(userId, authConfigId, options?)` (replaces `composio.connectedAccounts.initiate(...)`).
-- Python: `composio.connected_accounts.link(user_id, auth_config_id, **options)` (replaces `composio.connected_accounts.initiate(...)`).
-
-The return shape is the same — both methods give you a `redirect_url` (or `redirectUrl`) and a `wait_for_connection()` / `waitForConnection()` helper. See the [migration guide](/docs/auth-configuration/migrating-initiate-to-link) and the [changelog entry](/docs/changelog/2026/04/24).
-
-**Not affected by error 600:** custom auth configs (your own OAuth app) and non-OAuth schemes (API key, bearer token, basic auth) continue to work on `POST /api/v3/connected_accounts` indefinitely.
-
## Rate limiting
When you hit rate limits, you'll receive a `429` status code. See [Rate Limits](/reference/rate-limits) for details on limits by plan and best practices for handling rate limit errors.