Platform support across UniPost.
Use this page to understand what UniPost supports today across Twitter/X, LinkedIn, Instagram, Threads, TikTok, YouTube, Pinterest, Bluesky, and Facebook. The goal here is macro-level implementation guidance: which destinations exist, how the publish model works across them, where analytics and webhooks fit, and when you need to drop into a platform-specific guide.
Platform names in the UniPost API
Wherever the API accepts a platform — as a query filter, a request body field, or a path segment — UniPost uses the lowercase, URL-safe identifier listed below. Use this exact value when calling endpoints like GET/v1/accounts, POST/v1/accounts/connect, or POST/v1/connect/sessions.
| Network | API platform value |
|---|---|
| Twitter / X | twitter |
linkedin | |
instagram | |
| Threads | threads |
| TikTok | tiktok |
| YouTube | youtube |
| Bluesky | bluesky |
facebook | |
pinterest |
Platform Quick Reference
UniPost currently documents nine publishing destinations in the public platform guides. Each guide expands on media rules, validation behavior, and example request bodies for that network.
| Platform | Text | Images | Video | Threads | Analytics | Guide |
|---|---|---|---|---|---|---|
| Twitter/X | ✓ | ✓ | ✓ | ✓ | ✓ | View |
| ✓ | ✓ | ✓ | — | ✓ | View | |
| — | ✓ | ✓ | — | ✓ | View | |
| Threads | ✓ | ✓ | ✓ | ✓ | ✓ | View |
| TikTok | — | ✓ | ✓ | — | — | View |
| YouTube | — | — | ✓ | — | ✓ | View |
| — | ✓ | ✓ | — | ✓ | View | |
| Bluesky | ✓ | ✓ | ✓ | ✓ | — | View |
| Facebook (Beta) | ✓ | ✓ | ✓ | — | — | View |
Getting Started
The platform pages below explain destination-specific limits and payload options. For the shared post creation, local media upload, and async result flow, use the Publishing guide.
platform_posts[] request shape.Connect an Account
Create a Post
Cross-Post to Multiple Platforms
Platform-Specific Features
Each network still has its own behavior, and UniPost exposes that difference where it matters instead of pretending every destination works the same.
| Platform | First Comment | Audience / Privacy | Surface Controls | Playlist / Tags | Direct Credentials |
|---|---|---|---|---|---|
| Twitter/X | ✓ | ✓ | — | — | ✓ |
| — | ✓ | — | ✓ | — | |
| ✓ | — | ✓ | — | ✓ | |
| Threads | — | ✓ | — | — | — |
| TikTok | — | — | ✓ | — | — |
| YouTube | — | — | — | ✓ | — |
| — | ✓ | ✓ | — | — | |
| Bluesky | — | ✓ | — | — | ✓ |
| Facebook (Beta) | — | — | — | — | — |
Analytics Coverage
Which analytics KPIs are clearly represented in UniPost's current public analytics docs? This matrix only marks metrics that are explicitly documented today.
| Platform | Impressions | Reach | Likes | Comments | Views | Docs |
|---|---|---|---|---|---|---|
| Twitter/X | ✓ | — | ✓ | ✓ | — | View |
| ✓ | ✓ | ✓ | ✓ | — | View | |
| ✓ | ✓ | ✓ | ✓ | — | View | |
| Threads | ✓ | — | ✓ | ✓ | — | View |
| TikTok | — | — | — | — | — | View |
| YouTube | ✓ | — | — | — | — | View |
| ✓ | — | ✓ | ✓ | ✓ | View | |
| Bluesky | ✓ | — | — | — | — | View |
| Facebook (Beta) | — | — | — | — | — | View |
Webhooks
Developer webhooks are the current push-delivery mechanism across platforms. They cover async publish outcomes such as post.published, post.partial, and post.failed, plus account lifecycle events like account.connected and account.disconnected.
That means the macro pattern is consistent even when platform behavior is not: publish once, then either poll the post resource or subscribe to webhooks for final outcome.
API Reference
The fastest path through the current platform surface is usually:
- OAuth connect for OAuth platforms, or direct credentials for Bluesky.
- Connect sessions for customer-owned account onboarding.
- Create post for publish and scheduling.
- Validate post for preflight checks before publish.
- Media API when your workflow starts from local files instead of hosted URLs.
- Analytics and Developer webhooks for reporting and async delivery tracking.