@devries-cameron20 / composio-1 / commits / f92e6a27e
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.

docs: document post-auth success page branding in white-labeling authentication (#3247)

## Summary of Changes - Updated `docs/content/docs/white-labeling-authentication.mdx` to list four branding exposure points instead of three - Added table row for the post-auth success page (described generically without internal domain details) - Added new "Redirecting users after authentication" section showing how to pass `callbackUrl` to `session.authorize()` to bypass the default Composio-branded success page - Included cross-reference to the existing detailed `callbackUrl` documentation in the "Manually authenticating users" article ## Reasoning - Users following the white-labeling guide could complete all three steps and still have Composio branding visible on the post-auth success page - The `callbackUrl` parameter is documented in other articles but not referenced from the white-labeling article where users trying to achieve full white-labeling would naturally look - The default post-auth redirect is a distinct fourth branding exposure point that was missing from the article's overview table Co-authored-by: decimal-pr-bot[bot] <264021074+decimal-pr-bot[bot]@users.noreply.github.com>

decimal-pr-bot[bot] committed May 4, 2026 at 23:13 UTC f92e6a27ea53c901b140140664a07c8109e11a1c
1 file changed +30 -1
docs/content/docs/white-labeling-authentication.mdx
+30 -1
@@ -4,13 +4,14 @@ description: Remove Composio branding from your auth flows
4 keywords: [branding, own oauth, custom redirect, white label]
5 ---
6
7 -There are three places where Composio branding shows up during authentication:
7 +There are four places where Composio branding shows up during authentication:
8
9 | Where | What users see | How to fix |
10 |-------|---------------|------------|
11 | [**Connect Link page**](#customizing-the-connect-link) | Composio logo and name on the hosted auth page | Change logo + app title in dashboard |
12 | [**OAuth consent screen**](#using-your-own-oauth-apps) | "Composio wants to access your account" on Google, GitHub, etc. | Use your own OAuth app |
13 | [**Browser address bar**](#routing-the-callback-through-your-domain) | `backend.composio.dev` flashes during OAuth redirect-back | Proxy the redirect through your domain |
14 +| [**Post-auth success page**](#redirecting-users-after-authentication) | Composio-branded success page after OAuth completes | Pass a `callbackUrl` when initiating the connection |
15
16 ## Customizing the Connect Link
17
@@ -239,6 +240,34 @@ flowchart TD
240 For FAQs and setup guides for individual toolkits, browse the [toolkits page](/toolkits).
241 </Callout>
242
243 +## Redirecting users after authentication
244 +
245 +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()`:
246 +
247 +<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
248 +<Tab value="Python">
249 +```python
250 +connection_request = session.authorize(
251 + "gmail",
252 + callback_url="https://your-app.com/callback"
253 +)
254 +```
255 +</Tab>
256 +<Tab value="TypeScript">
257 +```typescript
258 +import { Composio } from '@composio/core';
259 +const composio = new Composio({ apiKey: 'your_api_key' });
260 +const session = await composio.create("user_123");
261 +// ---cut---
262 +const connectionRequest = await session.authorize("gmail", {
263 + callbackUrl: "https://your-app.com/callback",
264 +});
265 +```
266 +</Tab>
267 +</Tabs>
268 +
269 +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).
270 +
271 ## What to read next
272
273 <Cards>