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

> Lists the replies under one LinkedIn comment, oldest first, each with its author, text, time, reaction breakdown and `ext.is_submitter` (true when the reply is by the post's author). Called without `cursor` it returns the whole thread. Called with the parent's `ext.previous_replies_token` as `cursor` it returns only the replies older than the newest one, which /v1/linkedin/post/comments already carries in `comment.replies`, so the two calls together are the thread with no overlap. Pass the parent comment's `comment.id`, or its `comment.ext.urn`, as `comment_id`; the urn is the faster route on posts published as images, video or documents. A thread read without `cursor` takes about 20 seconds, and up to about 30 on the first comment of such a post when only the bare id is passed.

TL;DR: `GET /v1/linkedin/post/comments/replies` 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. |
| `comment_id` | yes | The parent comment's `comment.id` from /v1/linkedin/post/comments, or its `comment.ext.urn` (urn:li:comment:(ugcPost:<post>,<comment>)). |
| `cursor` | no | LinkedIn cursor. |
| `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 each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. 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/replies" \
  --data-urlencode "url=https://www.linkedin.com/feed/update/urn:li:activity:7501466755261820928" \
  --data-urlencode "comment_id=7501480403283886080" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I get the replies to a LinkedIn comment?

Send a GET request to /v1/linkedin/post/comments/replies with both the post URL and the comment_id in the query. SocialCrawl returns every reply to that specific comment, each with the replier's identity, text, and reaction count.

### Where do I find the comment_id to pass in?

Each comment returned by /v1/linkedin/post/comments carries its own comment_id. Take that value and pass it to this endpoint along with the post URL to expand that comment's reply thread.

### How do I paginate through the replies?

Use the cursor (or page) returned in the response and pass it back on the next call to fetch more replies. Keep going until the reply list comes back empty.

### How much does the LinkedIn Comment Replies API cost?

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

### Why is this a separate endpoint from post comments?

LinkedIn nests replies under each top-level comment, so replies are fetched per comment. This endpoint takes one comment_id and expands its thread, letting you get depth only where you need it.

### Can I rebuild an entire LinkedIn comment thread?

Yes. Call /v1/linkedin/post/comments to list top-level comments, then call this endpoint with each comment_id that has a non-zero reply count to pull its replies and assemble the complete thread.

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 fetch replies to a specific LinkedIn comment via API
- How to rebuild a full LinkedIn comment thread with SocialCrawl