linkedin/
post-comments

The LinkedIn Post Comments API collects public comments exposed with a known LinkedIn post, including normalized text, author context, timestamps, relationship IDs, and visible response counts.

LinkedIn Post Comments API

Single post URL
Public comment text
Response snapshot
0.5 credits / result
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

LinkedIn Post Comments

A LinkedIn post comment is a public response attached to one known post; this endpoint turns the comments exposed with that post into separate records with available text, public author fields, publication and collection times, source relationships, likes, and reply counts. Returned order is source-dependent, and a visible reply count does not mean reply bodies were included.

LinkedIn Post Comments API 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.

LinkedIn Post Comments API Parameters

ParametersRequiredDescription
urlRequiredRequired public LinkedIn post URL using /posts/, /pulse/, or /feed/update/urn:li:activity or /feed/update/urn:li:share.

How to Use the LinkedIn Post Comments API

Submit a supported public post URL to the LinkedIn Post Comments API, 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

LinkedIn Post Comments API 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 text from the LinkedIn Post Comments API 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.

LinkedIn Post Comments API 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 request property the LinkedIn Post Comments API accepts.
  • 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.

Beyond the LinkedIn Post Comments API, use these APIs when you need a different type of public LinkedIn data.

  • LinkedIn Profiles API — Normalize public profile identity, roles, location, visible audience counts, experience, education, and skills from profile URLs.
  • LinkedIn Companies API — Normalize public company descriptions, websites, logos, visible audience and employee counts, industries, locations, and specialties.
  • LinkedIn Posts API — Collect public post text, authors, visible engagement, media, publication time, type, and hashtags from supported URLs.
  • LinkedIn Jobs API — Normalize public job titles, companies, descriptions, locations, qualifications, employment details, application links, and available salary fields.
  • LinkedIn Company Jobs API — Discover public job listings from prepared LinkedIn /jobs/ URLs with normalized role, company, location, employment, experience, remote, salary, and timing fields.
  • LinkedIn Company Posts API — Discover public posts from LinkedIn company-page URLs with text, author context, media, hashtags, timestamps, and visible engagement.

Explore other platforms

Combine LinkedIn data with public data from other supported social platforms.

LinkedIn Post Comments API — FAQ

LinkedIn Post Comments API is a programmatic interface for collecting public comments exposed with one known LinkedIn post and returning normalized text, public author context, timestamps, relationship IDs, and available like and reply counts.

Submit one public http or https LinkedIn URL using a /posts/ or /pulse/ path, or a /feed/update/ path whose URN identifies an activity or share.

No. It processes the comment array exposed with the post response. A next_cursor on the completed SocQ task only pages through result records already stored for that task.

The endpoint does not perform a separate reply-expansion request. A comment may have replies_count without the reply bodies being present in the returned records.

Those fields are nullable because the public source does not always expose them. A missing like or reply count remains null and is not changed to zero.

No. It means the collection exposed no usable public comment records at that time; access, visibility, and source response conditions can affect what is available.

Each successfully stored comment record costs 0.5 SocQ credits, with no base charge. The pre-run estimate assumes 100 results, while final billing follows the actual stored result count; an empty result has no result charge.