White-labeling authentication
White-labeling lets you use your own OAuth apps instead of Composio’s. Users will see your app name on consent screens instead of “Composio”.
By default, OAuth screens show Composio’s branding:

With white-labeling, they’ll see your app name and logo.
Create an OAuth app
Create a developer app in the toolkit’s developer portal. You’ll need the client ID and client secret. Set the callback URL to:
For step-by-step guides on creating OAuth apps for some toolkits, see composio.dev/auth.
Create auth config
Create an auth config in the Composio dashboard:
- Go to Authentication management → Create Auth Config
- Select the toolkit (e.g., GitHub)
- Choose OAuth2 scheme
- Enter your Client ID and Client Secret
- Select the scopes you need
- Click Create
Copy the auth config ID (e.g., ac_1234abcd).
For detailed instructions with screenshots, see Custom auth configs.
Mixing custom and Composio-managed auth
You can white-label some toolkits while using Composio’s managed credentials for others:
Custom redirect domain
When users authenticate, they briefly see backend.composio.dev in their browser URL. Composio needs to receive the OAuth callback to capture and store the authentication tokens.
If you need to hide this URL (for enterprise compliance or complete white-labeling), you can proxy the redirect through your own domain:
- Set your OAuth app’s redirect URI to your domain:
- Create an endpoint that forwards the OAuth callback to Composio:
- Update your auth config in the Composio dashboard to use your custom redirect URI:

This makes the OAuth flow go through your domain first, then to Composio for token storage.