Social Media Analytics API: Posts Overview and Platform Insights in UniPost

A social media API should not stop at publishing. Once your app sends posts to TikTok, Instagram, Threads, Pinterest, and the rest of your social stack, users immediately ask what happened next. UniPost Analytics gives developers a normalized Posts Overview plus platform-specific drilldowns for the networks that expose deeper native metrics.

Most teams begin with a publish button. The second feature request is usually a reporting screen: did the post publish, which platform performed best, and what should the product show when one network exposes reach while another exposes views or outbound clicks?

Posts Overview: one place for published content performance

Posts Overview is the normalized layer. It answers how each piece of content performed after UniPost published it, regardless of whether the destination was a short video, an image post, a Thread, or a Pin. This is the right surface for product dashboards, customer reports, campaign tables, and agent workflows that need a reliable result after publishing.

• Use GET /v1/posts/:post_id/analytics to inspect one post across the accounts it was published to.
• Use GET /v1/analytics/summary for account-wide performance snapshots.
• Use GET /v1/analytics/by-platform when your UI needs to compare platforms inside the same reporting period.
• Keep unavailable metrics explicit. A platform that does not expose saves should show unavailable data, not a fabricated zero.

Platform Analytics: native metrics when the platform has more to say

Platform Analytics is the drilldown layer. It keeps the normalized analytics model, then adds the native fields a specific provider exposes. This is useful when users want to inspect the platform itself: TikTok public videos, Instagram Business media, Threads replies and reposts, or Pinterest board and Pin performance.

Why platform metrics do not all match

Social platforms do not expose a universal analytics schema. Instagram Business accounts can expose reach and saves for media. TikTok's approved analytics scopes focus on profile stats and public video metrics. Threads centers conversation metrics like replies, reposts, and quotes. Pinterest cares about impressions, saves, and outbound clicks. UniPost keeps those differences visible so your product can make honest UI decisions.

How a developer workflow fits together

A typical UniPost analytics workflow is: connect social accounts, publish posts, read delivery status, then fetch analytics for the published content. The same connected account IDs used for publishing are used when the dashboard drills into platform analytics.

curl "https://api.unipost.dev/v1/posts/post_abc123/analytics?refresh=true" \
  -H "Authorization: Bearer $UNIPOST_API_KEY"

curl "https://api.unipost.dev/v1/analytics/by-platform?range=30d" \
  -H "Authorization: Bearer $UNIPOST_API_KEY"

For account-level metrics, use Account Metrics. For post-level results, start with Post Analytics. If you want to see the productized platform surfaces first, compare the public previews for TikTok, Instagram, Threads, and Pinterest.

FAQ