OAuth and Review
OAuth and app review requirements by platform
Account connection is usually the hardest part of social publishing. This guide explains what to plan for before production launch.
Last verified 2026-06-23
Planning checklist
Plan OAuth and app review alongside product design, not after the first customer asks for a production connection.
Redirect URLsRegister production and dev callback URLsKeep app, staging, and dev domains explicit.
ScopesRequest only what the workflow needsOver-broad scopes slow review and create trust issues.
Demo contentPrepare review videos and screenshotsPlatforms often need proof of how permissions are used.
Token storageKeep native tokens out of browsersUniPost handles this in hosted connection flows.
Fallback pathUse quickstart while native review is pendingDo this only where quickstart mode fits the customer experience.
FAQ
Can I use UniPost credentials forever?
Quickstart credentials are useful for testing and some hosted flows, but white-label production often needs your own approved platform credentials.
Who owns platform review?
The app owner usually owns review artifacts and platform approval. UniPost provides the connection and publishing infrastructure around that process.