Hosted Connect (White-label branding)
Configure the Hosted Connect Profile your customers see before platform OAuth. This page maps to Developer → Hosted Connect in the dashboard; Platform Credentials live in their own guide.
At a glance
| Question | Answer |
|---|---|
| Dashboard page | Developer → Hosted Connect |
| What it controls | The UniPost-hosted pre-OAuth page: logo, display name, primary color, and attribution |
| What it does not control | The official platform OAuth app, consent screen, app review, or quota. Configure those in Platform Credentials. |
| Credential source | UniPost shared OAuth app or workspace Platform Credentials |
| Plan shape | Hosted Connect profile branding starts on Basic. Basic applies branding to one shared custom platform slot; Growth, Team, and Enterprise apply it to all supported platforms. Attribution removal depends on plan. |
| Best use case | Customer-facing SaaS onboarding where the connection handoff should look like your product |
Mental model
White-label branding is the Hosted Connect Profile your end users see before they continue to Instagram, YouTube, TikTok, LinkedIn, or another platform. It is independent from Platform Credentials. You can combine either Hosted Connect profile with either credential source; on Basic, both surfaces must use the same selected platform slot.
| Layer | Dashboard page | What it changes |
|---|---|---|
| Hosted Connect Profile | Developer → Hosted Connect | Logo, display name, color, and Powered by UniPost attribution on the UniPost page |
| Platform Credentials | Developer → Platform Credentials | Which official platform app and quota are used during OAuth |
| Connect Sessions | API | The URL your backend gives an end user to start account connection |
Dashboard setup
API setup
The dashboard is the simplest path. If you manage profile branding from your own admin tooling, update the profile directly. These fields are read at render time by Hosted Connect.
Credential source
Hosted Connect branding does not decide quota ownership. If a workspace has approved Platform Credentials for the requested platform, UniPost can use that app and quota. If a session allows quickstart fallback and no workspace credentials exist, UniPost can use its shared OAuth app. On Basic, the requested platform must match the workspace's shared custom platform slot for branding or Platform Credentials to apply.
| Question | Answer |
|---|---|
| Can a default Hosted Connect page use workspace Platform Credentials? | Yes, when the workspace plan and custom platform slot allow that platform |
| Can a branded Hosted Connect page use UniPost shared OAuth? | Yes, when quickstart fallback is allowed and the requested platform is inside the plan's branding scope |
| Where do I configure developer app client ID and secret? | Platform Credentials |
| Where do I configure logo/name/color? | Developer → Hosted Connect |