How to White-Label Albato OAuth in your SaaS

Last update: 12/7/2025 · 4 min read

---

IN THIS ARTICLE

There are 2 most typical ways your users can authenticate their accounts on 3rd party platforms:

1. API Key
2. OAuth

1. API key

This authentication type requires your user to enter a secret key, so no Albato branding will show up when creating such connections.

2. OAuth

This authorization displays the OAuth application owner details on permission pages. Since Albato owns authentication for all apps listed in its marketplace, by default your users will see the Albato logo in the OAuth pop-up.

How to White-Label Albato OAuth Generic Integration Hub

Albato constantly creates a generic Integration Hub application for the most popular connectors. Here is the list of apps where Integration Hub is currently available. We’re continuously adding Integration Hub to more apps, so the list will keep expanding.

For the apps in the list above, you can choose to show Integration Hub in OAuth popups from day one. This is the easiest and fastest way to white-label user-facing authentication pages without burdening your team with extra work.

Examples of Integration Hub in user-facing OAuth pop-ups:

Your Native OAuth

Alternatively, you can create your own OAuth application for a fully white-label user experience, although this will require some effort from your team.

To create your own OAuth app you, follow these steps:

1. Register a developer’s account—you can set it up on most platforms that support OAuth.
2. Create your OAuth app.
3. Add the following redirect_URI in the OAuth app settings:
   https://r.integrations-hub.com/oauth/back/state
4. Share the client_id and client_secret values of your OAuth app with Albato.

Here is a good example you can tap into:
Slack OAuth guideline

Below is an example of Knack, one of our clients using our embedded integrations. While their integrations run on Albato, Knack’s customers see the Knack logo when connecting to Slack and other systems.