Skip to main content
Enterprise-only feature. Social Topics is not self-serve. Contact us at [email protected] to discuss access.
Social Topics gives enterprise teams a managed LinkedIn topic monitoring pipeline plus read APIs for the posts and engagers Trigify collects on their behalf.

​
What It Does

  • creates keyword-based LinkedIn topic searches for your organisation
  • starts discovery immediately when a topic is created
  • tracks matched posts across searches with shared post deduplication
  • schedules follow-up engagement collection for tracked posts
  • exposes both search-level and post-level engagement reads through the API

​
Typical Workflow

  1. Create a topic search with POST /v1/topics.
  2. Review active searches with GET /v1/topics or inspect one search with GET /v1/topics/{id}.
  3. Pull deduplicated search-level engagers from GET /v1/topics/{id}/engagements.
  4. Drill into one tracked post with GET /v1/topics/{id}/posts/{postId}/engagements.
  5. Check allocated billing-period credits with GET /v1/topics/{id}/credits-summary.
  6. Query the broader engagement graph with POST /v1/social/mapping.

​
Monitoring Cadence

StageCadenceDetails
Initial kickoffImmediatePOST /v1/topics creates the search and immediately starts LinkedIn discovery.
Initial engagement hydrationImmediatePosts linked during the create-time run are hydrated right away so the first engagement results are available without waiting for cron.
Ongoing rediscoveryDaily at 06:00 UTCACTIVE topic searches are rediscovered once per day. PAUSED, STOPPED, deleted, and expired searches are excluded.
Backfill schedulerEvery 5 minutesTrigify checks for tracked posts whose next engagement scrape is due.
Follow-up engagement scrapesDay 1, Day 3, Day 5After a post is first tracked, Trigify performs follow-up engagement scrapes on the Day 1, Day 3, and Day 5 intervals.
Search lifecycle30 daysTopic searches automatically expire after 30 days unless they are stopped or deleted sooner.

​
Example Workflow

# 1. Create a new topic search
curl -X POST https://api.trigify.io/v1/topics \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "AI Infrastructure Buyers",
    "keywords": ["ai infrastructure", "model serving", "vector database"],
    "keywords_and": ["buying", "vendor selection"],
    "keywords_not": ["hiring", "job opening"],
    "job_titles": ["CTO", "VP Engineering", "Head of Data"],
    "time_frame": "past-week",
    "max_results": 50,
    "content_type": "posts",
    "sort_by": "date_posted"
  }'

# 2. List current searches
curl -X GET "https://api.trigify.io/v1/topics?page=1&page_size=10" \
  -H "x-api-key: YOUR_API_KEY"

# 3. Read deduplicated engagers for one topic
curl -X GET "https://api.trigify.io/v1/topics/topic_abc123xyz/engagements?page=1&page_size=25" \
  -H "x-api-key: YOUR_API_KEY"

# 4. Read one tracked post only
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"

# 5. Review billing-period credit allocation
curl -X GET "https://api.trigify.io/v1/topics/topic_abc123xyz/credits-summary" \
  -H "x-api-key: YOUR_API_KEY"

# 6. Query the engagement graph collected from your topics
curl -X POST https://api.trigify.io/v1/social/mapping \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "engaged_with_keywords": ["ai infrastructure", "model serving"],
    "engaged_with_days": 14,
    "engaged_with_topic_strength": 2,
    "job_titles": ["CTO", "VP Engineering"],
    "company_sizes": ["51-200", "201-500"],
    "page": 1,
    "page_size": 10
  }'

​
Billing Model

ActionCredits
Create topic search0
New post collected1
New engagement collected5
Read endpoints (GET /v1/topics...)0
Social Mapping querycharged per returned result
Credits are charged when Trigify collects new data, not when you create or read a topic search. Social Mapping is billed separately from Social Topics monitoring and returns the spend in the x-spent-credits header.

​
Authentication And Permissions

  • Send your API key in x-api-key.
  • Required plan: ENTERPRISE or CUSTOM.
  • Topic management uses topics:write.
  • Topic reads use topics:read.
  • Engagement reads use topics:engagements:read.
  • Social Mapping uses social:mapping:read.

​
Endpoint Guide