Manage Connections
Learn how to direct users to manage their third party connections
This guide explains how to redirect users to the BlueNexus "Manage Connections" white-label application so they can manage the services (Google, Notion, etc.) connected to their BlueNexus account.
Before following this guide, ensure you've completed Steps 1-4 to create and authenticate BlueNexus accounts for your users.
You can customize the appearance of your white-label web page by uploading your logo and configuring your application details in the developers.md portal.
Authentication Handoff
To redirect your users to the white-label application, you'll initiate an authentication handoff. This process securely transfers the user's authenticated session from your application to the BlueNexus white-label application.
Overview
The redirection to the white-label application works as follows:
Your app requests a handoff code from the BlueNexus API
Your app redirects the user to the white-label application with the code
The user adds or remove connections to their account. (Note: Additional capabilities may be added in the future)
The user is then redirected back to your app via the provided
redirectUriYour app can refresh its data (for instance to get the updated user's connections)
The Two Essential Steps
Step 1: Request a Handoff Code
Call the handoff initialization endpoint:
Response:
Parameters:
redirectUri: Where to redirect the user after they finish on the white-label pageintent: Set to"connections"to allow users to manage their connected services (Google, Notion, etc.)
The handoff code expires in 30 seconds. You must redirect the user immediately after receiving the code.
Step 2: Redirect to the White-Label Web Page
Redirect the user to your white-label URL with the code as a query parameter:
Implementation Examples
Web Application
Mobile Application (React Native)
Handling User Return
After users complete their actions on the white-label page, they'll be redirected back to your redirectUri. You should refresh your data at this point.
Web Application
Mobile Application
Configure your app to handle deep links:
Expo (app.json):
app.json):Listen for deep link events:
Security Considerations
The authentication handoff uses several security measures:
Short-lived codes: Handoff codes expire in 30 seconds
IP fingerprinting: We currently use IP fingerprinting as an extra layer of security, matching the initialization with the finalization. In the case of the initialization is executed from your server and therefore a different IP than where the user will open the white-label web app, please contact us.
One-time use: Each code can only be used once
Scoped access: The web session is limited to the requested intent (e.g., the
connectionsintent grant connection-related scopes only)
Last updated

