LinkedIn Post comments API
List comments on a LinkedIn post - full text, commenter name/URL/job title, timestamps, and engagement.
$2.90/1k req, pay per request, no subscription.
{"id":Â "7477792100112233445","commentary":Â "This lines up with what we saw rolling out usage-based billing last year. The hardest part was never the pricing model, it was getting the ledger to reconcile in real time.","url":Â "https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7477791740645564416%2C7477792100112233445%29","createdUtc":Â 1758153600,"pinned":Â true,"edited":Â false,"actor":Â {...},"engagement":Â {...}}
Pricing and providers
LinkedIn Post comments API pricing: one API, 4 interchangeable providers
The cheapest provider serves first. If it fails, the next one takes over in the same call.
capped at $0.143 per request1 result$0.0014350 results$0.0715100 results$0.143 capYou are charged for what comes back. Lower the limit to pay less - and no single request can cost more than the cap, however much comes back.4HoneybeeBackup 399.82% uptime4076ms p5010.5% of calls10.5%566 calls$2.20/1k resultsup to $0.22 / requestMetered per result returned$0.0022 per result
capped at $0.22 per request1 result$0.002250 results$0.11100 results$0.22 capYou are charged for what comes back. Lower the limit to pay less - and no single request can cost more than the cap, however much comes back.
Try it
Get LinkedIn post comments in one request
This sample shows 19 of 20 fields. See every field
{
"found": true,
"data": {
"items": [
{
"id": "7477792100112233445",
"commentary": "This lines up with what we saw rolling out usage-based billing last year. The hardest part was never the pricing model, it was getting the ledger to reconcile in real time.",
"url": "https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7477791740645564416%2C7477792100112233445%29",
"createdUtc": 1758153600,
"pinned": true,
"edited": false,
"actor": {
"id": "ACoAAB99887766ccddeeff",
"name": "Priya Nakamura",
"type": "profile",
"linkedinUrl": "https://www.linkedin.com/in/priya-nakamura-fin",
"position": "Head of Finance Engineering at Northwind Financial",
"image": "https://media.licdn.com/dms/image/C4E03AQZ9n2h/dp_200/0/167?e=175"
},
"engagement": {
"likes": 214,
"comments": 6
}
},
{
"id": "7477792200223344556",
"commentary": "Great conversation. Curious whether the same approach to dunning applies once you are dealing with multi-currency subscriptions, that is where we keep hitting edge cases.",
"url": "https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7477791740645564416%2C7477792200223344556%29",
"createdUtc": 1758150000,
"pinned": false,
"edited": true,
"actor": {
"id": "ACoAAB88776655bbccddee",
"name": "Marcus Delgado",
"type": "profile",
"linkedinUrl": "https://www.linkedin.com/in/marcus-delgado-payments",
"position": "Product Manager, Billing at Cedarlane Health",
"image": "https://media.licdn.com/dms/image/C4E03AQY8n2h/dp_200/0/167?e=175"
},
"engagement": {
"likes": 58,
"comments": 2
}
},
{
"id": "7477792300334455667",
"commentary": "We are hosting a follow-up session on this exact topic next month. Would love to have some of the folks in this thread join the panel.",
"url": "https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7477791740645564416%2C7477792300334455667%29",
"createdUtc": 1758146400,
"pinned": false,
"edited": false,
"actor": {
"id": "urn:li:organization:4471203",
"name": "Vantage Robotics",
"type": "company",
"linkedinUrl": "https://www.linkedin.com/company/vantage-robotics",
"position": "Autonomous inspection drones",
"image": "https://media.licdn.com/dms/image/C560BAQF7n2h/logo_200/0/167?e=175"
},
"engagement": {
"likes": 19,
"comments": 0
}
}
]
}
}Full parameter and response reference - every field, type, and example for this endpoint.
Reference
One request, one response shape.
Every field you send and every field you get back, each with a real example.
Last verified 2026-10-31 · uptime and latency measured over 30d
Request body
JSON, posted to this endpoint.
- urlstring
https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ
Full URL of the LinkedIn post to list comments for.
- limitinteger
10
Maximum number of comments to return.
- postedLimitenum
Only return comments posted within this window (default any).
Response
JSON, one example value per field.
The commenter (a profile or a company).
- idstring
ACoAAB99887766ccddeeff
LinkedIn identifier of the commenter.
- imagestring
https://media.licdn.com/dms/image/C4E03AQZ9n2h/dp_200/0/167?e=175
Profile picture URL of the commenter. Populated whenever the provider has data for the entity.
- linkedinUrlstring
https://www.linkedin.com/in/priya-nakamura-fin
Canonical LinkedIn URL of the commenter. Populated whenever the provider has data for the entity.
- namestring
Priya Nakamura
Display name of the commenter. Populated whenever the provider has data for the entity.
- positionstring
Head of Finance Engineering at Northwind Financial
Commenter's headline or job title as displayed. Populated whenever the provider has data for the entity.
- typestring
profile
Commenter kind, e.g. 'profile' or 'company'.
The post's comments. Populated whenever the provider has data for the entity.
- commentarystring
This lines up with what we saw rolling out usage-based billing last year. The hardest part was never the pricing model, it was getting the ledger to reconcile in real time.
Full text of the comment. Populated whenever the provider has data for the entity.
- createdUtcnumber
1758153600
UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds. Populated whenever the provider has data for the entity.
- editedboolean
false
Whether the comment has been edited.
- idstring
7477792100112233445
Unique identifier of the comment. Populated whenever the provider has data for the entity.
- pinnedboolean
true
Whether the comment is pinned on the post.
- urlstring
https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7477791740645564416%2C7477792100112233445%29
Canonical permalink URL of the comment. Populated whenever the provider has data for the entity.
Engagement metrics for the comment.
- commentsinteger
6
Number of replies to the comment.
- likesinteger
214
Number of likes on the comment.
- foundboolean
true
Whether comments were found for the post.
- reason"not_found"
Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.
FAQ
About the LinkedIn Post comments API
The AnyAPI LinkedIn Post comments API returns LinkedIn post comments data as normalized JSON from one POST call to /v1/run/linkedin.post_comments. List comments on a LinkedIn post - full text, commenter name/URL/job title, timestamps, and engagement. AnyAPI routes each request across 4 sources and falls back automatically when one fails. It costs from $2.90 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 99.9% of LinkedIn post comments calls through AnyAPI succeeded, with a median response time of 2.3 seconds across 5,938 measured calls.