# LinkedIn Post Comments API (https://www.socialcrawl.dev/platforms/linkedin/post-comments)

> Returns a paginated list of comments on a LinkedIn post, with commenter identity, text, reaction breakdown, pin/edit flags, and reply counts. LinkedIn shows the newest reply of each thread under its comment, and so does this endpoint: it is in `comment.replies`, with its own author, text and time. `engagement.replies` is the thread's full count. When a thread has older replies than the one shown, the comment also carries `ext.previous_replies_token`; pass it as `cursor` to /v1/linkedin/post/comments/replies to read the rest, or call that endpoint without `cursor` for the whole thread. A one-reply thread has no token because its only reply is already in `comment.replies`. `ext.is_submitter` is true when the commenter wrote the post (LinkedIn's Author badge). A reply's `id` is LinkedIn's comment id when LinkedIn sends one; otherwise it is a stable id built from the parent comment's id (`<parent id>:<8 hex>`). A post with no comments returns an empty page for free, and that empty answer is cached for 1 hour; send `Cache-Control: no-cache` to read it again sooner.

TL;DR: `GET /v1/linkedin/post/comments` costs 5 credits per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `url` | yes | Full URL of the LinkedIn post. It has to carry the post's ACTIVITY id, either `https://www.linkedin.com/feed/update/urn:li:activity:<id>` or `https://www.linkedin.com/posts/<slug>-activity-<id>-<code>`. A `urn:li:share:` or `urn:li:ugcPost:` URL names a different id for the same post and is rejected with a 400 before any credits are charged, because it cannot be resolved to the post. Every endpoint that lists posts publishes the activity form as `post.url`, so copy that field rather than rebuilding the URL from `post.id`, which is not always the activity id. |
| `page` | no | Page number for pagination (default 1). |
| `post_type` | no | Upstream post type: 'activity' (default) or 'ugc'. (activity \| ugc) |
| `sort_order` | no | Comment ordering: 'relevance' or 'recent'. (recent \| relevance) |
| `since` | no | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off the page, and the page that reaches one ends the walk: `next_cursor` is not returned and `pagination.stopped_at` is `since`. Sending it sets the newest-first sort shown in this endpoint's sort parameter (any other sort value is a free 400). The page still costs what a page costs, so you pay for the pages you walk and no more. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| `until` | no | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/linkedin/post/comments" \
  --data-urlencode "url=https://www.linkedin.com/feed/update/urn:li:activity:7244804629786419202" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I get the comments on a LinkedIn post?

Send a GET request to /v1/linkedin/post/comments with the full LinkedIn post URL in the url parameter. SocialCrawl returns a paginated list of comments, each with the commenter's identity, text, reaction breakdown, reply count, and pin or edit flags.

### Can I sort LinkedIn comments by relevance or recency?

Yes. Pass sort_order=relevance (the LinkedIn default) or sort_order=recent to control ordering. Relevance surfaces the most-engaged comments first; recent returns them newest-first for monitoring active threads.

### How do I paginate through all the comments?

Add the page parameter and increment it to fetch each successive page of comments. Continue until the response returns an empty list, which marks the end of the thread.

### How much does the LinkedIn Post Comments API cost?

Each page costs 5 credits on the advanced tier, no matter how many comments come back on that page. New accounts get 100 free credits with no credit card, enough for 20 pages of comments.

### What fields come back for each comment?

Each comment includes the commenter's name and profile, the comment text, reaction count and breakdown, reply count, and pin and edit flags. Use the reply count with /v1/linkedin/post/comments/replies to fetch nested replies.

### Can I use LinkedIn comments for social listening?

Yes. Comment text and commenter identity make this endpoint useful for sentiment analysis, spotting engaged prospects, and monitoring how audiences respond to competitor or industry posts.

See the full LinkedIn API: https://www.socialcrawl.dev/platforms/linkedin

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How to scrape LinkedIn post comments with SocialCrawl
- How to sort LinkedIn comments by relevance or recency via API