Skip to main content
GET
/
v1
/
topics
/
{id}
/
posts
/
{postId}
/
engagements
curl -X GET "https://api.trigify.io/v1/topics/topic_abc123xyz/posts/7356241888074958848/engagements?page=1&page_size=25" \
  -H "x-api-key: YOUR_API_KEY"

{
  "message": "<string>",
  "success": true,
  "data": [
    {
      "id": "<string>",
      "prospect_id": "<string>",
      "linkedin_post_id": "<string>",
      "discovery_interval": 123,
      "created": "<string>",
      "prospect": {
        "full_name": "<string>",
        "linkedin_url": "<string>",
        "job_title": "<string>",
        "company": "<string>"
      },
      "engagement": {
        "type": "<string>",
        "text": "<string>"
      }
    }
  ],
  "pagination": {
    "page": 123,
    "page_size": 123,
    "total_count": 123,
    "total_pages": 123
  }
}
Use this endpoint to retrieve the collected engagers for one tracked LinkedIn post within a Social Topics search.
Enterprise-only endpoint. Contact us at [email protected] to discuss access.
This is a free read endpoint. Credits are charged when Trigify collects new engagement results, not when you retrieve them.

​
Overview

This post-level view focuses on one tracked LinkedIn post inside one Social Topics search. Unlike the search-level engagements endpoint, this view does not collapse the full topic down to one row per prospect across all tracked posts.

​
Authentication And Permissions

  • Send your API key in x-api-key
  • Required permission: topics:engagements:read
  • Required plan: ENTERPRISE or CUSTOM
curl -X GET "https://api.trigify.io/v1/topics/topic_abc123xyz/posts/7356241888074958848/engagements?page=1&page_size=25" \
  -H "x-api-key: YOUR_API_KEY"

​
Monitoring Context

The returned rows reflect engagement collection from:
  • the immediate hydration run that happens when the topic is first created
  • the scheduled Day 1, Day 3, and Day 5 follow-up scrapes
  • the backfill scheduler that checks for due post scrapes every 5 minutes

​
Example Response

{
  "success": true,
  "message": "Post engagements retrieved",
  "data": [
    {
      "id": "topic_engager_post_abc123",
      "prospect_id": "prospect_9vL1m1aX3fV8Qp",
      "linkedin_post_id": "7356241888074958848",
      "discovery_interval": 1,
      "created": "2026-03-08T08:42:11.000Z",
      "prospect": {
        "full_name": "Jordan Lee",
        "linkedin_url": "https://www.linkedin.com/in/jordan-lee",
        "job_title": "VP of Engineering",
        "company": "Northstar Cloud"
      },
      "engagement": {
        "type": "like",
        "text": null
      }
    },
    {
      "id": "topic_engager_post_def456",
      "prospect_id": "prospect_u82b6aTpQ2mLm4",
      "linkedin_post_id": "7356241888074958848",
      "discovery_interval": 3,
      "created": "2026-03-09T08:42:11.000Z",
      "prospect": {
        "full_name": "Priya Sharma",
        "linkedin_url": "https://www.linkedin.com/in/priya-sharma",
        "job_title": "CTO",
        "company": "Lighthouse Data"
      },
      "engagement": {
        "type": "comment",
        "text": "We are consolidating vendors in this area now."
      }
    }
  ],
  "pagination": {
    "page": 1,
    "page_size": 25,
    "total_count": 2,
    "total_pages": 1
  }
}

​
When To Use This View

Use the search-level endpoint when you want one deduplicated row per engaged prospect across the entire topic. Use this endpoint when you want to inspect the engagement collected for one specific tracked post.

Headers

​
x-api-key
string

Path Parameters

​
id
string
required

Topic search ID

​
postId
string
required

LinkedIn post ID

Query Parameters

​
page
integer
default:1

Page number

Required range: x >= 1
​
page_size
integer
default:10

Items per page

Required range: 1 <= x <= 100

Response

200 - application/json

Paginated post engagers

​
message
string
required
​
success
boolean
required
​
data
object[]
required
​
pagination
object
required