REST API
Analytics
Introduction

Analytics

The Analytics API returns normalized analytics for published FeedHive posts and connected social accounts.

Platforms expose different metrics. A missing metric is omitted, while a real zero is returned as 0. Do not assume similarly named metrics are measured identically across platforms.

Freshness

FeedHive uses the following read flow:

  1. A snapshot collected within the last 15 minutes is returned immediately.
  2. If the snapshot is missing or older, FeedHive attempts a just-in-time provider refresh.
  3. The provider refresh is limited to 12 seconds.
  4. If refresh fails and an older snapshot exists, that snapshot is returned as a stale fallback.

Failed refreshes use a server-controlled cooldown. Repeating a request cannot force repeated provider calls during that cooldown.

Normalized metrics

The metrics object only includes provider-applicable values returned for that target:

  • Metric values are JSON numbers.
  • Zero and missing are distinct: 0 is preserved; missing values are omitted.
  • Raw provider payloads are never included.
  • collected_at is the ISO 8601 time at which FeedHive collected the returned snapshot.
  • stale: true means the data is a usable older snapshot returned after refresh failed or timed out.

Post metrics can include impressions, reach, views, likes, comments, shares, clicks, saves, engagements, engagement rates, video views, watch time, and subscriber changes. Account metrics can include followers, subscribers, profile/page views, impressions, reach, clicks, engagements, conversations, bookings, orders, and post count. Actual availability depends on the provider and account permissions.

IDs

  • Use a normal FeedHive post ID from the Posts API for post analytics.
  • Use a social account ID from GET /socials for account analytics.
  • You do not need FeedHive's internal publication IDs.

Authentication and rate limits

Analytics uses the same bearer token and ownership context as every other Public API endpoint. Resources outside that context are hidden with a not-found response.

The standard Public API rate limit of 60 requests per minute applies. Analytics also has provider-facing freshness and cooldown controls, so polling faster does not force fresher upstream data.

EndpointsEndpoints