API reference organized by workflow.
Instead of making you scan one giant long-form page, the API reference is split by what you are trying to do: connect accounts, publish posts, validate drafts, inspect analytics, or receive events.
Authentication
Every API request uses Bearer auth with your UniPost API key. Dashboard-authenticated routes exist separately for the product UI, but the public API reference focuses on API-key integrations.
Endpoint groups
| Group | What it covers | Start here |
|---|---|---|
| Accounts | List, connect, disconnect, and inspect social accounts | Social Accounts |
| Connect sessions | Hosted onboarding for end-user-owned accounts | Connect Sessions |
| Posts | Create, validate, schedule, draft, and preview content | Create Post |
| Analytics | Inspect performance and workspace-level summaries | Analytics |
| Webhooks | Subscribe to publish and account events | Webhooks |
Connect sessions
Use Connect sessions when your customers need to connect their own social accounts inside your product. This is where UniPost stops being just a posting API and becomes account-onboarding infrastructure.
Managed users
Managed Users groups connected accounts by your own `external_user_id` so you can model end users cleanly across platforms.
Validate
Validate is the recommended preflight endpoint for automation and AI workflows. It catches content issues before anything is written or published.
Drafts
Drafts and preview links give you a review surface before content is published. This is especially useful when an LLM or automation is generating the first draft.
Preview links
Preview links are designed for review and collaboration flows. They let a human inspect the platform-specific output before the final publish step.
Media
Use the media library when you want UniPost to manage upload references and resolve media IDs server-side instead of depending on public URLs.
Analytics
Analytics includes both per-post performance and workspace rollups, so you can power dashboards, summaries, and agent workflows from one layer.
Account health
Account health gives you a fast signal when a connected account is healthy, degraded, or disconnected.
Billing
Billing and usage endpoints let you map product behavior back to plan limits and account usage.
Errors
UniPost uses structured error responses so clients can distinguish validation issues, authorization problems, conflicts, and transient server failures.
Existing detailed endpoint pages already live under the new shell. Start with the core publish path.
Use the social accounts reference when you need account IDs, filtering, or managed account lookups.
Webhooks are where most production integrations become observable and debuggable.