Provider integrations

Self-hosting makes you responsible for provider applications, approval, callback URLs, and secrets. Configure one provider, restart OpenPost, connect one real account, and publish a small test post before adding more.

How configuration works

Set legacy variables for X, LinkedIn, Threads, and Mastodon, or use the structured OPENPOST_PROVIDER_APPS JSON registry. The registry also supports Facebook, Instagram, TikTok, YouTube, Pinterest, Telegram, and Discord bot mode. Inject the variable through your deployment secret store so client secrets never enter shell history or Compose files.

Open Settings → Instance → Configuration → Provider apps when your instance administrator manages encrypted database rows. Environment values take precedence over matching database rows. Restart after changing provider configuration.

Provider portals: LinkedIn Developers, X Developer Portal, Google Cloud Console, TikTok for Developers, Pinterest Developers, Bluesky, Mastodon, Discord Developer Portal, and Telegram BotFather.

Every OAuth callback uses this shape:

https://your-domain.example/api/v1/accounts/<provider>/callback

Set OPENPOST_APP_URL to the public origin. The callback registered with the provider must match the configured URL exactly. OPENPOST_MEDIA_URL must be public HTTPS for providers that fetch media themselves.

Guides

• LinkedIn
• X
• YouTube
• TikTok
• Pinterest
• Bluesky and Mastodon
• Discord and Telegram