White Label Integration
Multi-tenant OAuth2 with your branding
Transform OAuth2 integrations into seamless customer experiences! White labeling lets your users authenticate with services using your branding while Airweave handles all the complex OAuth2 infrastructure behind the scenes.
🎨 Your Brand, Our Infrastructure
Customers see “YourApp wants to access Google Drive” instead of “Airweave wants to access Google Drive” - but you get all the power of Airweave’s data sync platform.
Why White Label?
Users see your company name throughout the entire OAuth experience
OAuth flows feel like a native part of your application
Automatic data isolation per customer with zero configuration
How It Works
Quick Start
1. Create White Label Configuration
First, set up your white label integration with your OAuth2 app credentials:
REST API
Python SDK
Node.js SDK
2. Generate Customer Auth URLs
For each customer who wants to connect their account:
REST API
Python SDK
Node.js SDK
3. Handle OAuth Callback
When the customer completes OAuth, handle the callback:
REST API
Python SDK
Node.js SDK
Complete Integration Example
Here’s a full example showing how to integrate white labeling into a React application:
Example Demo Application
What Happens Behind the Scenes
🔐 Secure Token Management
Airweave securely stores OAuth2 tokens and handles automatic refresh. Your customers never need to re-authenticate unless they revoke access.
🏗️ Automatic Source Connections
Each successful OAuth flow creates a source connection in the specified collection, ready to sync data immediately.
🛡️ Multi-Tenant Isolation
Customer data is automatically isolated using the state
parameter you provide. No risk of data mixing between customers.
⚡ Immediate Sync
If sync_immediately
is true, data sync starts in the background as soon as the connection is created.
Security & Best Practices
🔒 OAuth2 Credentials Security
Never expose credentials in frontend code. Always handle OAuth2 flows on your backend and store credentials securely.
Use HTTPS everywhere for redirect URLs and origins Validate state parameters to prevent CSRF attacks Store secrets securely using environment variables or secret managers Rotate credentials regularly for enhanced security
Cache auth URLs temporarily to reduce API calls Use webhooks to get notified when syncs complete Monitor sync status to handle failures gracefully Set up alerts for authentication errors
Troubleshooting
❌ OAuth Flow Fails
Common causes:
- Incorrect redirect URL in OAuth app settings
- Missing required scopes
- Invalid client credentials
Solutions:
- Verify redirect URL matches exactly (including protocol)
- Check OAuth app configuration in the service’s developer console
- Ensure client_id and client_secret are correct
🚫 CORS Errors
Common causes:
- Origin not included in
allowed_origins
- HTTP vs HTTPS mismatch
Solutions:
- Add your domain to the
allowed_origins
field - Ensure protocol matches (use HTTPS in production)
⚠️ Sync Failures
Common causes:
- Insufficient OAuth permissions
- Token expiration without refresh token
Solutions:
- Request broader OAuth scopes
- Verify refresh tokens are being stored and used
Next Steps
Complete API documentation for white label endpoints and examples
Explore OAuth2 requirements for all 28+ supported sources
Join our Discord for help and community support
🎉 Ready to Go!
Your customers will now see a professional, branded OAuth experience while you get all the benefits of Airweave’s powerful data synchronization platform.