Skip to main content
POST
/
v1
/
post
/
comments
curl -X POST https://api.trigify.io/v1/post/comments \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "postUrn": "7196224250288955393",
    "page": 1
  }'
{
  "message": "<string>",
  "success": true,
  "data": {
    "comments": [
      {
        "isPinned": true,
        "isEdited": true,
        "threadUrn": "<string>",
        "urn": "<string>",
        "createdAt": 123,
        "createdAtString": "<string>",
        "permalink": "<string>",
        "text": "<string>",
        "author": {
          "name": "<string>",
          "urn": "<string>",
          "id": "<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
        },
        "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
            }
          }
        ]
      }
    ],
    "total": 123,
    "totalPage": 123,
    "currentPage": 123
  }
}
Extract detailed comments from any LinkedIn post to analyze engagement patterns, identify prospects, and understand community discussions around individual content.

Overview

The Post Comments API reveals all comments on any LinkedIn post, along with detailed information about each commenter including their professional background, engagement metrics, and replies. Perfect for analyzing how audiences respond to content and identifying engaged prospects from personal or professional LinkedIn activity.

Authentication

Requires a valid API key with the track:post:comments permission.
curl -X POST https://api.trigify.io/v1/post/comments \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "postUrn": "7196224250288955393",
    "page": 1
  }'

Response Structure

The endpoint returns paginated comment data including:

Pagination Information

  • Current Page: The page number of results returned
  • Total Pages: Total number of pages available
  • Total Count: Total number of comments across all pages
  • Comments: Array of comment objects for the current page

Comment Data

  • Comment Content: Full text content of the comment
  • Author Information: Name, title, LinkedIn profile, and professional details
  • Engagement Metrics: Likes, reactions, and social activity counts
  • Thread Information: Comment URN, timestamps, and permalink
  • Replies: Nested replies to the comment with full author details
  • Moderation: Whether the comment is pinned or edited

Author Details

Each comment includes comprehensive author information:
  • Professional Profile: Name, title, LinkedIn URL, and profile details
  • Company Context: Current role and professional background
  • Social Presence: LinkedIn profile metrics and engagement history

Credit Usage

This endpoint charges 1 credit per comment returned. The number of credits spent is returned in the x-spent-credits response header. Examples:
  • Page with 25 comments: Uses 25 credits
  • Page with 10 comments: Uses 10 credits
  • Page with no comments: Uses 0 credits
Pagination Strategy:
  • Each page can contain multiple comments (varies by post activity)
  • Popular posts may have hundreds of comments across multiple pages
  • Plan your credit usage based on expected comment volume

Use Cases

  • Social Selling: Find prospects who are actively engaging with relevant industry content
  • Lead Generation: Identify warm leads who comment on posts related to your products or services
  • Influencer Outreach: Discover engaged community members and thought leaders
  • Content Research: Analyze what types of posts generate meaningful discussions
  • Competitive Intelligence: Monitor who engages with competitor or industry leader content
  • Community Building: Identify active participants in your industry conversations
  • Account-Based Marketing: Find additional contacts within target companies who are engaged on LinkedIn

Post URN Format

The postUrn parameter should be the LinkedIn postโ€™s unique identifier:
  • Extract from post URLs: "7196224250288955393" (the numeric part)
  • Found in LinkedIn post URLs after activity-: /posts/username_activity-7196224250288955393-abcd
  • Also available in LinkedInโ€™s internal post references
The URN will be validated to ensure itโ€™s a proper LinkedIn post identifier format.

Pagination Best Practices

When working with posts that have many comments:
  1. Start with Page 1: Always begin with page: 1 to get the most recent comments
  2. Check Total Pages: Use the totalPage field to determine how many pages are available
  3. Monitor Credits: Track your credit usage across pages to stay within budget
  4. Implement Limits: Set a maximum number of pages to retrieve to control costs
  5. Cache Results: Store comment data to avoid re-fetching the same information

Comment Structure

Post comments include rich data about engagement:

Engagement Metrics

  • Like Count: Number of likes on the comment
  • Reaction Counts: Detailed breakdown by reaction type (appreciation, praise, etc.)
  • Reply Count: Number of nested replies
  • Total Reactions: Aggregate engagement across all reaction types

Temporal Data

  • Creation Time: Timestamp and formatted date strings
  • Relative Time: Human-readable time since posting
  • Thread Context: Position within the conversation flow

Reply Threads

Comments may include nested replies with full author details and engagement metrics, allowing you to analyze complete conversation threads and identify the most engaged participants in discussions.

Advanced Features

Batch Processing

For analyzing multiple posts efficiently, consider:
  • Processing posts in batches to optimize API usage
  • Implementing rate limiting to respect API constraints
  • Caching comment data for posts that donโ€™t change frequently

Sentiment Analysis

Comment text can be processed for:
  • Sentiment analysis to understand audience reception
  • Keyword extraction to identify trending topics
  • Engagement quality assessment based on comment length and depth

Network Analysis

Use comment data to:
  • Map professional networks and connections
  • Identify influential voices in your industry
  • Track engagement patterns across related posts

Differences from Company Post Comments

This endpoint is designed for individual LinkedIn posts and differs from company post comments in several ways:
  • Content Type: Focuses on personal and professional individual posts rather than corporate content
  • Audience: Often includes more diverse, personal networking conversations
  • Engagement Patterns: May include more casual, relationship-building interactions
  • Permission: Requires track:post:comments rather than track:company:comments
  • Optimization: Tuned for individual content creator posting patterns

Headers

x-api-key
string
required

Body

application/json
postUrn
string
required

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

Minimum string length: 1
page
integer
default:1

The page number for pagination (defaults to 1)

Required range: x >= 1

Response

200 - application/json

Successfully retrieved post comments

message
string
required
success
boolean
required
data
object
required