# LinkedIn Comments API. Pay per record.

> Every comment on a LinkedIn post, with the commenter's name, headline and followers. $0.002 per comment.

Canonical: https://apiforagents.dev/platforms/linkedin/comments-api · Updated 2026-10-21

Get the comments on any LinkedIn post: who commented, their headline and follower count, what they wrote, when, and the likes and replies on each comment. Up to ten posts per call.

- Price: $0.002 / comment
- Billed: Per record
- Free to start: $0.10
- Endpoint: POST /v1/linkedin

## What people build with the LinkedIn Comments API

- **Engaged leads from a post.** The people who commented on a competitor's launch post are telling you they care. List them.
- **Measure a campaign.** Read every comment on your own posts, with who said it and how many people agreed.
- **Community research.** See who shows up in the comments of the voices in your market.

## Quote it, then run it

1. free quote: the exact price, nothing charged:

```bash
curl -X POST https://apiforagents.dev/v1/linkedin \
  -H "Authorization: Bearer $AFA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"op":"postComments","subjects":["https://www.linkedin.com/posts/<post-id>"],"limit":25,"estimateOnly":true}'
```

2. the same call, run:

```bash
curl -X POST https://apiforagents.dev/v1/linkedin \
  -H "Authorization: Bearer $AFA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"op":"postComments","subjects":["https://www.linkedin.com/posts/<post-id>"],"limit":25}'
```

## Inputs

Everything you can send in one postComments call. Required inputs first.

| Input | Type | What it does |
|---|---|---|
| subjects * | text list | Post URLs. 1-10 items |
| includeReplies | boolean | true: nested replies come back under their parent comment, not only top-level comments. |
| postedWithin | enum |  |
| limit | integer | 1-100 |

## What comes back

The fields of every row, always present. Nothing is guessed: a value that could not be measured is null, and the answer's coverage says why.

| Field | Type |
|---|---|
| commentId | string |
| commentUrl | string |
| postUrl | string |
| postUrn | string |
| commenterProfileId | string |
| commenterHandle | string |
| commenterName | string |
| commenterHeadline | string |
| commenterUrl | string |
| commenterAvatarUrl | string |
| commenterType | string |
| commenterFollowers | integer |
| isAuthor | boolean |
| edited | boolean |
| likes | integer |
| replies | integer |
| reactions | list of object |
| body | string |
| commentedAt | string |
| mentions | list of string |
| postAuthor | string |
| postAuthorHandle | string |
| postAuthorUrl | string |
| postAuthorHeadline | string |
| postAuthorAvatarUrl | string |
| postAuthorProfileId | string |
| postAuthorType | string |
| postText | string |
| postPostedAt | string |
| postMediaUrl | string |
| postLikes | integer |
| postComments | integer |
| postReposts | integer |
| details | object |

details is always the last field: everything else the source sent for that row, under our own field names. Its keys depend on the source that answered, so read them defensively; it is {} when there is nothing more.

## A sample answer

Made-up names and values in the real field names, so you can see the shape before you spend anything.

| commenterHandle | commenterName | commenterHeadline | body | likes | replies |
|---|---|---|---|---|---|
| priya-nair | Priya Nair | Product Lead at Ledgerly | This matches what we saw. Did churn move too? | 34 | 3 |
| tom-becker | Tom Becker | Founder, Brightdesk | Saving this for our next planning week. | 12 | 0 |
| ananya-rao | Ananya Rao | Head of Marketing at Paylane | @Priya Nair yes, churn in month one fell by a third. | 21 | 0 |

## Pricing

Pay as you go, in US dollars, per record. No subscription, nothing expires, $5 first top-up, and every new agent starts with $0.10 free.

| Request | Records | At the list price |
|---|---|---|
| One comment | 1 | $0.002 |
| 10 comments | 10 | $0.02 |
| A full page | 100 | $0.2 |

These are per-record list prices. Some calls also carry a minimum, such as a page of search results, so a small request can cost more than the table shows. The quote ("estimateOnly": true) is free, gives the most your exact request can cost, and the charge then settles to what came back. Records that do not come back are refunded.

## Try it without writing code

- [Open the LinkedIn Comments API in the playground](https://apiforagents.dev/dashboard/run?platform=linkedin&op=postComments): The playground runs any endpoint by hand: pick a platform and what you want from it, fill a short form named in plain words (or press Use sample input), see the free quote on the Run button, run it, then read the answer as a table or JSON and download it as CSV or JSON. The same call is written out as cURL, Python and Node while you type.

## Why this one, and not a scraper you run yourself

- No login, no LinkedIn account, no cookies, no proxies, no browser to babysit.
- When the site changes its pages, your request stays the same: keeping the reads working is our job, not yours.
- A fetch that fails costs nothing: it is named in the answer with a reason, and the quote says the most a call can cost before it runs.

## Questions

### What does the LinkedIn Comments API return?

One row per comment: comment id and URL, the post URL, the commenter's handle, name, headline, profile URL and follower count, whether they are the author, whether it was edited, likes, replies, the text and when it was posted.

### Can I get replies too?

Yes, set includeReplies to pull nested replies.

### How much does it cost?

$0.002 per comment returned, up to a hundred per call.

## Why API for Agents

- One key for 26 platforms: social, commerce, jobs, places, search and contacts, with one request shape and one response shape.
- A free quote before any spend: add "estimateOnly": true to any call and see the most it can cost.
- Pay per record in US dollars. No subscription, nothing expires, top-ups from $5.
- $0.10 free to try, no card. An AI agent can sign itself up in one request; a person claims it later.
- Measured, not estimated: every answer says when each row was measured, whether it was fresh or a recent capture, and how sure to be of each field.
- Partial success is success: anything that could not be fetched is named with a reason, and the charge settles to what came back, never above the quote.
- Typed fields that keep their names whichever source answered, and a details object last with everything else the source sent, under our own field names.
- Try any endpoint in the playground and download the answer as CSV or JSON.

## Start

The playground runs any endpoint by hand: pick a platform and what you want from it, fill a short form named in plain words (or press Use sample input), see the free quote on the Run button, run it, then read the answer as a table or JSON and download it as CSV or JSON. The same call is written out as cURL, Python and Node while you type. Open it at https://apiforagents.dev/dashboard/run?platform=linkedin&op=postComments (sign in first).

Agents register at https://apiforagents.dev/auth.md (one POST, $0.10 free). People: https://apiforagents.dev/docs#start. Prices: https://apiforagents.dev/pricing.md