Analytics

Batch version of GET /analytics/posts/{id}. Pass a comma-separated list of numeric OmniSocials post ids in ids and get each post's latest per-platform metrics back in a single request (thread posts are summed across their parts, same as the single-post endpoint). Built for sync clients that would otherwise call the single-post endpoint once per post and hit the 100 requests/minute rate limit. Up to 100 ids per call; page through larger sets in batches. Every requested id is returned (in request order); ids with no collected analytics come back with an empty platforms object rather than being omitted, so clients can map results 1:1 to the ids they sent. Reads stored snapshots from our database, the same data as the single-post endpoint, so it never calls the social platforms live.

Totals for the workspace of this API key over a period (period, default 30 days, or start_date and end_date), with a breakdown per platform. Requires the analytics:read scope.

Latest stored account-level snapshot per connected platform, on or before the requested date. Snapshots are collected daily. Metric semantics vary by platform (see the AccountAnalytics schema). LinkedIn rows hold that day's impressions (period: "daily"). A LinkedIn profile row also keeps the all-time total of all of the member's posts in impressions_lifetime; when LinkedIn serves no daily breakdown, its impressions is that lifetime total and the row carries period: "lifetime". Each metrics object carries a note explaining its scope where semantics are non-obvious.

Recommended day/hour posting slots for one platform, computed from the workspace's own posting history (publish time × engagement of every post published on that platform, recency-weighted, outlier-damped). Times are bucketed in the requesting user's timezone (overridable via timezone). When the workspace has fewer than 15 analyzed posts on the platform, a static industry-average table is returned instead: basis flips from own_data to defaults and posts_needed says how many more published posts unlock personalized recommendations. Grid scores are relative within the platform (100 = the best slot). Requires the analytics:read scope.