Get post replies/comments

Fetch all comments and replies for a specific published post from a particular social media account. Specify the target account using network (required) and optionally username. If the post was published to only one account on that network, username can be omitted. When the post was published to multiple accounts on the same network, omitting username returns a 400 with the available usernames to disambiguate. By default only top-level comments are returned; set include_replies=true to nest each comment's replies under it (Facebook, Instagram, LinkedIn - a single reply tier; Threads nests to any depth). Note that Threads returns the whole conversation flat when include_replies is omitted, so nested replies still appear there as top-level entries. Comments are not supported on every network - TikTok, Pinterest, and Google Business Profile do not expose a comments API, and YouTube comments are not yet supported; these networks will return an error.

Response keys: read data, which returns the same comment shape for every network (id, author, text, created_at, like_count, and nested replies when requested). The replies key is deprecated: it preserves the per-network shape this endpoint returned before the cross-network format existed, so it differs by network and never carries nested replies. It is kept only so existing integrations do not break.

get/v1/posts/{id}/replies

Request

Base URL: https://api.outstand.so
URL: https://api.outstand.so/v1/posts/{id}/replies
Auth: none declared

Path parameters

idstring required

Query parameters

networkstring required

Example:x

Social network name (e.g., 'x', 'threads')

usernamestring

Example:mycompany

Username or nickname of the social account that published the post. Optional when the post was published to only one account on the given network.

include_repliesboolean

When 'true', nest each comment's replies under it (post → comment → replies). Defaults to top-level comments only. Fetching replies on LinkedIn issues an extra API call per comment.

resolve_author_namesboolean

LinkedIn only: when 'true', resolve each commenter's URN into author_name (plus author_username, author_avatar_url and author_profile_url where LinkedIn provides them). Every other network already returns a readable author and ignores this. Some LinkedIn commenters cannot be resolved (for example members who limit their off-LinkedIn visibility) - those come back with author_name: null and author left as the URN. LinkedIn does not allow member profile data to be stored: cache a resolved name for at most 24 hours and re-fetch after that.

Response

Replies retrieved successfully

successboolean required

Example response

{
  "success": true,
  "replies": [
    {
      "id": "x_123456789_1704067200000",
      "author": "johndoe",
      "text": "Great post!",
      "created_at": "2025-01-15T10:30:00Z",
      "like_count": 5,
      "platform_specific": {}
    }
  ],
  "data": [
    {
      "id": "x_123456789_1704067200000",
      "author": "johndoe",
      "author_name": "John Doe",
      "author_username": "johndoe",
      "author_avatar_url": "https://media.licdn.com/dms/image/example.jpg",
      "author_profile_url": "https://www.linkedin.com/in/johndoe",
      "text": "Great post!",
      "created_at": "2025-01-15T10:30:00Z",
      "like_count": 5,
      "platform_specific": {}
    }
  ]
}

Changes

No recorded changes to this operation across all 1 revision of this API.