Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
TypeScript agentic-aiagentsaiai-agentsaiagentsdeveloper-toolsfunction-callinggpt-4javascriptjsllmllmopsmcppythonremote-mcp-serverssetypescript
docs: document post-auth success page branding in white-labeling authentication (#3247)
decimal-pr-bot[bot]f92e6a27ea53
diff --git a/docs/content/docs/white-labeling-authentication.mdx b/docs/content/docs/white-labeling-authentication.mdxindex de2b8c624..9c8355a69 100644--- a/docs/content/docs/white-labeling-authentication.mdx+++ b/docs/content/docs/white-labeling-authentication.mdx@@ -4,13 +4,14 @@ description: Remove Composio branding from your auth flowskeywords: [branding, own oauth, custom redirect, white label]----There are three places where Composio branding shows up during authentication:+There are four places where Composio branding shows up during authentication:| Where | What users see | How to fix ||-------|---------------|------------|| [**Connect Link page**](#customizing-the-connect-link) | Composio logo and name on the hosted auth page | Change logo + app title in dashboard || [**OAuth consent screen**](#using-your-own-oauth-apps) | "Composio wants to access your account" on Google, GitHub, etc. | Use your own OAuth app || [**Browser address bar**](#routing-the-callback-through-your-domain) | `backend.composio.dev` flashes during OAuth redirect-back | Proxy the redirect through your domain |+| [**Post-auth success page**](#redirecting-users-after-authentication) | Composio-branded success page after OAuth completes | Pass a `callbackUrl` when initiating the connection |## Customizing the Connect Link@@ -239,6 +240,34 @@ flowchart TDFor FAQs and setup guides for individual toolkits, browse the [toolkits page](/toolkits).</Callout>+## Redirecting users after authentication++By default, after OAuth completes, users land on a Composio-hosted success page that shows Composio branding. To bypass this page and send users to your own domain instead, pass a `callbackUrl` when calling `session.authorize()`:++<Tabs groupId="language" items={['Python', 'TypeScript']} persist>+<Tab value="Python">+```python+connection_request = session.authorize(+ "gmail",+ callback_url="https://your-app.com/callback"+)+```+</Tab>+<Tab value="TypeScript">+```typescript+import { Composio } from '@composio/core';+const composio = new Composio({ apiKey: 'your_api_key' });+const session = await composio.create("user_123");+// ---cut---+const connectionRequest = await session.authorize("gmail", {+ callbackUrl: "https://your-app.com/callback",+});+```+</Tab>+</Tabs>++After authentication, Composio redirects the user to your callback URL instead of the default success page. For full details on the parameters appended to your callback URL, see [Manually authenticating users → Redirecting users after authentication](/docs/authenticating-users/manually-authenticating#redirecting-users-after-authentication).+## What to read next<Cards>