Platform Credentials
Save official platform developer app credentials when you want OAuth consent and API quota to come from your own app instead of UniPost's shared OAuth apps.
Developer → Platform CredentialsOwn app identityOwn platform quotaSeparate from Hosted Connect
At a glance
| Question | Answer |
|---|---|
| Dashboard page | Developer → Platform Credentials |
| What it controls | Which official platform OAuth app and quota UniPost uses for future OAuth flows |
| What it does not control | The UniPost-hosted pre-OAuth page. Configure that in Hosted Connect (White-label branding). |
| Who can use it | Qualified paid plans. Basic supports one shared custom platform slot across Platform Credentials and Hosted Connect branding; Growth, Team, and Enterprise support all supported platforms. |
| Shared fallback | Connect Sessions can still use UniPost's shared OAuth app when allow_quickstart_creds is true and no workspace credential exists. |
How it works
Platform Credentials are workspace-level developer app credentials: client ID plus client secret for the official platform. They are independent from Hosted Connect branding, but Basic uses one shared custom platform slot for both surfaces. Quickstart and branded Hosted Connect flows can use either credential source when the plan, selected platform slot, and session settings allow it.
1
Create the app in the platform developer portal
Use the guide for the platform you need and enable the product, scopes, or API access required by your flow.
2
Allow-list UniPost callback URLs
Each OAuth platform has exact callback URLs. Copy them from the platform guide or from the dashboard row.
3
Save the client ID and secret
Open Developer → Platform Credentials and paste the app credentials into the matching platform row.
4
Create a fresh Connect Session
After saving credentials, start a new connection attempt so the OAuth flow uses the current platform app settings.
Platform guides
| Platform | Dashboard row | Developer portal | Review / approval |
|---|---|---|---|
| Meta | Meta (Instagram / Threads) | Meta for Developers | Plan for App Review / Advanced Access before broad production rollout, especially if you need public customer onboarding. |
| LinkedIn Developer Portal | The basic OIDC + posting flow is comparatively straightforward. Higher-tier LinkedIn products are where approval gets slower. | ||
| TikTok | TikTok | TikTok for Developers | Expect more scrutiny than LinkedIn. Build time for audit / review into the rollout plan, not after engineering is done. |
| YouTube | YouTube | Google Cloud Console | Scope verification may be needed depending on your rollout shape. Even before formal verification, start by proving the OAuth wiring with one real channel owner. |
| X / Twitter | X / Twitter | X Developer Portal | Access and feature availability are tier-dependent. Treat billing / plan approval as part of setup, not an afterthought. |