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, 14:45 UTC
docs(auth): point custom OAuth callback URL to v1 (UXE-261) (#4206)
## What Points all instructional docs (and the Python example) for custom OAuth credentials to the **v1** callback URL: `https://backend.composio.dev/api/v1/auth-apps/add` ...replacing the previously documented `https://backend.composio.dev/api/v3.1/toolkits/auth/callback`. ## Why The backend returns the **v1** URL as the default redirect URI for every toolkit (it's what flows into the generated `docs/public/data/toolkits.json`), and Consumer product expects v1 — but Consumer doesn't surface the callback URL, so users go to the docs, find the **v3.1** URL, and whitelist the wrong one in their OAuth app. Flagged as a top confusion in Go Live calls. Fixes [UXE-261](https://linear.app/composio/issue/UXE-261/update-docs-to-point-to-v1-callback-url). ## Files changed - `docs/.../authentication/programmatic-auth-configs.mdx` (ticket's primary target) - `docs/.../authentication/white-labeling-authentication.mdx` - `docs/.../auth-configuration/white-labeling.mdx` - `docs/.../auth-configuration/custom-auth-configs.mdx` - `python/examples/auth_configs.py` ## Deliberately NOT changed - **`docs/.../migration-guide/new-sdk.mdx`** — states *"The callback URL is now v3… The previous URL was v1"*. It documents the v1→v3 migration history; flipping it to v1 would make it self-contradictory. Left as-is. - **`docs/public/data/toolkits.json` / `ts/docs/api/toolkits.md`** — generated from the backend API, already v1. No manual edit. ## ⚠️ Open question worth confirming The migration guide says v3 is the *current* callback and v1 is *previous*. This PR points developers *back* to v1 to match Consumer. That's a real backend/product inconsistency, not just a docs typo — worth confirming with @rahul / @abhishek that v1 is genuinely the URL Consumer expects (and whether the migration guide messaging should be revisited separately). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
No changes.