Pinned by author
Priya Nakamura
Head of Finance Engineering at Northwind Financial
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.
Sep 18, 2025214Reply
Marcus Delgado
Product Manager, Billing at Cedarlane Health
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.
Sep 17, 202558Reply
Vantage Robotics
Autonomous inspection drones
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.
Sep 17, 202519Reply
{"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": {...}}
价格与服务商
LinkedIn 帖子评论 API 价格:一个 API,4 个可互换的服务商
最便宜的服务商优先响应。如果它失败,下一个会在同一次调用中接手。
每次请求封顶 US$0.1321 条结果US$0.0013250 条结果US$0.066100 条结果US$0.132(封顶)按实际返回的内容计费。调低返回数量上限即可少付,而且无论返回多少,单次请求都不会超过封顶价。4Honeybee备用 3可用率 99.56%p50 4085ms占调用的 11.9%11.9%895 次调用US$2.20/千条结果每次请求最多 US$0.22计量方式:每条结果,按实际返回每条结果 US$0.0022
每次请求封顶 US$0.221 条结果US$0.002250 条结果US$0.11100 条结果US$0.22(封顶)按实际返回的内容计费。调低返回数量上限即可少付,而且无论返回多少,单次请求都不会超过封顶价。
试一试
一个请求获取 LinkedIn 帖子评论
这个示例展示了 20 个字段中的 19 个。查看全部字段
{
"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
}
}
]
}
}完整的参数与响应参考:这个接口的每个字段、类型和示例。
参考
一个请求,一种响应结构。
你发送的每个字段和收到的每个字段,都附有真实示例。
最近验证于 2026-11-14 · 可用率和延迟按 30d 统计
请求体
JSON,POST 到这个接口。
- urlstring
https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ
要列出评论的 LinkedIn 帖子完整 URL。
- limitinteger
10
最多返回的评论数。
- postedLimitenum
只返回在此时间范围内发布的评论(默认不限)。
响应
JSON,每个字段一个示例值。
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.
常见问题
关于 LinkedIn 帖子评论 API
AnyAPI 的 LinkedIn 帖子评论 API 只需一次 POST 请求 /v1/run/linkedin.post_comments,就以统一格式的 JSON 返回 LinkedIn 数据。列出 LinkedIn 帖子下的评论:完整正文、评论者姓名/URL/职位、时间戳和互动数据。AnyAPI 会在 4 个数据源之间路由每个请求,某个数据源失败时自动切换。费用:每千次请求 US$2.90 起,以美元计价,无需订阅,也没有每月最低消费。过去 30 天,通过 AnyAPI 发起的 LinkedIn 帖子评论 API 调用中有 99.9% 成功,响应时间中位数为 2.3 秒,共测量 7,501 次调用。