Get published-post insights
Performance for one published post and its superpower: public/private replies, link-button clicks + CTR, reactions, comments, shares, auto-likes. Computed on demand (Amplitude reply funnels + a live Meta call), so it is slower than the plain post lookup. Covers up to the last 365 days; older posts come back with `isOldPost=true` and empty funnel metrics. `mediumId` is **required** (posts are per channel).
/posts/{postId}/insightsAuthorization
x-api-key x-date x-signature Your API key (the ApiKeys document id).
In: header
Current timestamp in ISO-8601 (must be fresh — within −5s..+60s of server time).
In: header
HMAC-SHA256 of the x-date string keyed by your secret, lowercase hex.
In: header
Path Parameters
The published post id.
Query Parameters
The channel id (from GET /channels).
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/posts/string/insights?mediumId=string"{}{ "message": "string"}{ "message": "string"}{ "message": "string"}{ "error": [ { "message": "string", "path": [ "string" ], "type": "string", "context": {} } ]}Get a published post
Fetch a single published post. `mediumId` is **required** — published posts are stored per channel.
List live comments for a post
Live comments for a published post, fetched fresh from the Meta Graph API and normalized across FB/IG. `mediumId` is **required** (it locates the channel + its access token). Paged natively: `limit` is passed down to Meta and the response carries `paging.after` (an opaque cursor — echo it back as `after` for the next page) plus `paging.hasMore`. Meta's raw paging object is never returned (its `next` URL embeds the channel access token).