Skip to main content
POST
/
v1
/
post
/
comments
/
replies
curl -X POST https://api.trigify.io/v1/post/comments/replies \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "postUrn": "7196224250288955393",
    "commentUrn": "urn:li:comment:(urn:li:ugcPost:7218979654638989312,7219337261564252161)",
    "previousCursor": "UFJFVklPVVNfMTc2NTkwMjg5NTY2Ml9DTEVBTg=="
  }'

{
  "message": "<string>",
  "success": true,
  "data": {
    "replies": [
      {
        "isPinned": true,
        "isEdited": true,
        "urn": "<string>",
        "createdAt": 123,
        "createdAtString": "<string>",
        "permalink": "<string>",
        "text": "<string>",
        "author": {
          "name": "<string>",
          "urn": "<string>",
          "username": "<string>",
          "linkedinUrl": "<string>",
          "title": "<string>"
        },
        "totalSocialActivityCounts": {
          "numComments": 123,
          "likeCount": 123,
          "appreciationCount": 123,
          "empathyCount": 123,
          "InterestCount": 123,
          "praiseCount": 123,
          "funnyCount": 123,
          "maybeCount": 123,
          "totalReactionCount": 123,
          "numShares": 123
        }
      }
    ],
    "count": 123,
    "previousCursor": "<string>",
    "hasMore": true
  }
}
Fetch paginated replies for a specific LinkedIn comment using the comment-level reply cursor exposed by the Post Comments API.
Enterprise-only endpoint. Contact us at [email protected] to discuss access.

​
Overview

Use this endpoint when a comment on POST /v1/post/comments advertises a previousCursor and you want to expand the rest of that comment thread. This endpoint is LinkedIn-only and returns a normalized Trigify response shape for consistency with POST /v1/post/comments.

​
Authentication

Requires a valid API key with the track:post:comments permission. Required plan: ENTERPRISE or CUSTOM. 
curl -X POST https://api.trigify.io/v1/post/comments/replies \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "postUrn": "7196224250288955393",
    "commentUrn": "urn:li:comment:(urn:li:ugcPost:7218979654638989312,7219337261564252161)",
    "previousCursor": "UFJFVklPVVNfMTc2NTkwMjg5NTY2Ml9DTEVBTg=="
  }'

​
Request Fields

  • postUrn: Numeric LinkedIn post id, identical to the value used with POST /v1/post/comments
  • commentUrn: Full LinkedIn comment URN returned by POST /v1/post/comments
  • previousCursor: Optional reply cursor returned by the comments response or a previous replies response
For backward compatibility, this endpoint also accepts legacy numeric comment ids if you cached comment data before the URN normalization change. New POST /v1/post/comments responses return a reply-compatible full comment URN.

​
Cursor Flow

  1. Call POST /v1/post/comments
  2. Read the target comment’s previousCursor
  3. Call POST /v1/post/comments/replies with that cursor
  4. If the mirrored upstream reply payload returns another previousCursor, reuse it for the next page

​
Response Structure

The endpoint returns:
  • replies: the reply items for this page
  • count: number of replies returned in this response
  • previousCursor: cursor to request the next page, or null when there is no next page
  • hasMore: boolean convenience flag derived from previousCursor

​
Credit Usage

This endpoint charges 1 credit per reply returned. The number of credits spent is returned in the x-spent-credits response header. Examples:
  • 2 replies returned: 2 credits
  • 25 replies returned: 25 credits
  • no replies returned: 0 credits

​
Notes

  • The response is normalized by Trigify for consistency with the existing comments API, while still preserving the upstream cursor flow.
  • If a comment does not include a previousCursor, there may be no additional reply pages to fetch.

Headers

​
x-api-key
string

Body

application/json
​
postUrn
string
required

The LinkedIn post URN to get replies from. ex: '7196224250288955393'

Minimum string length: 1
​
commentUrn
string
required

The LinkedIn comment URN returned by POST /v1/post/comments. Legacy numeric comment ids are also accepted for backward compatibility. ex: 'urn:li:comment:(urn:li:ugcPost:7218979654638989312,7219337261564252161)'

Pattern: ^(?:urn:li:comment:(\d+|\(.+\))|\d+)$
​
previousCursor
string

Cursor returned by the comments or replies response to fetch the next page of replies

Response

200 - application/json

Successfully retrieved post comment replies

​
message
string
required
​
success
boolean
required
​
data
object
required