Dynamo Developer DocsDynamo Developer Docs
External APIPosts

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).

GET/posts/{postId}/comments

Authorization

x-api-key x-date x-signature
x-api-key<token>

Your API key (the ApiKeys document id).

In: header

x-date<token>

Current timestamp in ISO-8601 (must be fresh — within −5s..+60s of server time).

In: header

x-signature<token>

HMAC-SHA256 of the x-date string keyed by your secret, lowercase hex.

In: header

Path Parameters

postId*string

The published post id.

Query Parameters

mediumId*string

The channel id (from GET /channels).

limit?integer

Max comments per page (passed natively to Meta).

after?string

Opaque page cursor — the paging.after of a previous response.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/posts/string/comments?mediumId=string"
{  "comments": [    {      "id": "string",      "message": "string",      "createdTime": "string",      "from": {        "id": "string",        "name": "string"      },      "permalink": "string"    }  ],  "paging": {    "after": "string",    "hasMore": true  }}
{  "message": "string"}
{  "message": "string"}
{  "message": "string"}
{  "message": "string"}
{  "message": "string"}
{  "error": [    {      "message": "string",      "path": [        "string"      ],      "type": "string",      "context": {}    }  ]}
{  "message": "string"}

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).

Export a post's stored comments to CSV

Export all of a post's **stored** comments (Firestore — same source as the in-app exporter, not a live Meta fetch) to a CSV uploaded to Storage, and return `{ totalCount, csvUrl }`. The storage filename is deterministic (`comments_<postId>.csv`) so re-exports overwrite rather than pile up. When there are no stored comments, `csvUrl` is `null` and `totalCount` is `0`. `mediumId` is **required**.