LinkedIn Post Comments API

LinkedIn Post Comments

Features

• One known post as the boundaryAccept one supported /posts/, /pulse/, or /feed/update/ URL and inspect the public comments exposed with that exact post.
• Normalized comment recordsReturn comment text with available ID, public URL, publication time, collection time, and public author fields in a stable comment schema.
• Available relationship contextPreserve parent_id and post_id when the source supplies them, while leaving those declared fields null when it does not.
• Visible response countersKeep likes_count and replies_count as nullable measurements instead of converting an unavailable counter to zero.

Parameters

How to Use

Submit a supported public post URL, follow the asynchronous task, and page through the comments stored for that completed task.

1. Choose one public LinkedIn URL whose path uses /posts/, /pulse/, or /feed/update/ with an activity or share URN.
2. Send it as url to /v1/linkedin/post-comments and save the returned task_id.
3. Poll /v1/tasks/{task_id} until the task succeeds or returns a failure.
4. Read data.results.items and follow next_cursor while has_more is true; that cursor pages stored SocQ results, not the upstream LinkedIn comment feed.

curl -X POST "https://api.socq.ai/v1/linkedin/post-comments" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://www.linkedin.com/posts/aagupta_what-you-need-to-know-ai-agents-activity-7354600338621906944-RvXR"}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

Best Use Cases

• Response review for a known post: Read the public comment text attached to a selected announcement, article, or campaign post without broad account discovery.
• Question and feedback triage: Route returned text for human review of questions, objections, or product feedback while keeping source links and author context.
• Public engagement snapshots: Compare available like and reply counts across returned comments and anchor the observation to collected_at.
• Source-linked comment archives: Store normalized comment records with the submitted post URL and available post_id or parent_id for later audit and retrieval.

Pro Tips

• Deduplicate the activity or share identifier before submitting repeated URL variants for the same post.
• Do not send results_limit, sorting, or reply-expansion fields; url is the only accepted request property.
• Treat returned order as source-dependent rather than chronological or relevance-ranked.
• Keep null distinct from zero for likes_count and replies_count because an unavailable counter is not evidence of no engagement.
• Do not infer sentiment, intent, seniority, lead quality, or automated behavior from the normalized fields alone.
• Continue through next_cursor only to read all comments already stored for the completed task; it does not request another LinkedIn comment page.

Related APIs