LinkedIn 主页评论 API

列出某个 LinkedIn 会员在他人帖子下留下的评论：评论正文、永久链接和时间戳，以及所评论的帖子、该帖子的作者和互动数据。

免费开始下载示例或 JSON

US$2.90/千次请求，按请求付费，无需订阅。

inJeff Weiner | Comments | LinkedIn

linkedin.com/in/jeffweiner08/recent-activity/comments/

Jeff Weiner's Activity

Comments

PostsCommentsImagesVideosDocuments

Jeff Weiner

Commented on Aisha Kapoor's post·Sep 21, 2025

Aisha Kapoor

New data from our workplace learning survey: companies that redesigned at least one core workflow around AI this year saw 3x the productivity lift of those that only added a chat assistant on top of existing processes.

This matches what we are seeing across our portfolio too. The teams that treat AI adoption as a workflow redesign problem, not a tooling purchase, are the ones pulling ahead.

LikeReply

API 返回的内容items[0]

{
"id": "urn:li:comment:(urn:li:activity:7481203945521098752,7481204988612345601)",
"commentary": "This matches what we are seeing across our portfolio too. The teams that treat AI adoption as a workflow redesign problem, not a tooling purchase, are the ones pulling ahead.",
"url": "https://www.linkedin.com/feed/update/urn:li:activity:7481203945521098752?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7481203945521098752%2C7481204988612345601%29",
"createdUtc": 1758470400,
"edited": false,
"isAuthor": false,
"actor": {...},
"engagement": {...},
... 还有 1 个字段}

可用率

100.00%

30d · 5,021 次调用

请求数

5,021

30d · 按周，近 12 周

响应时间

3.7s

中位数 · 30d

价格与服务商

LinkedIn 主页评论 API 价格：一个 API，2 个可互换的服务商

最便宜的服务商优先响应。如果它失败，下一个会在同一次调用中接手。

服务商，按调用顺序

1Alpaca优先响应可用率 100.00%p50 3601ms占调用的 77.7%77.7%3,899 次调用100.00%3601msUS$2.90/千次请求flat 2Hedgehog备用 1可用率 99.73%p50 3148ms占调用的 22.3%22.3%1,122 次调用99.73%3148msUS$3.86/千次请求flat

我需要次请求

你需支付

US$29.00

US$2.90/千次请求，只为实际用量付费。没有月度套餐。

有了 US$0.10 的初始余额，你的前 34 次请求免费。

试一试

一个请求获取 LinkedIn 主页评论

url*string要列出其在他人帖子下评论的 LinkedIn 会员主页完整 URL。limitinteger 1-100最多返回的评论数。postedLimitenum只返回在此时间范围内发布的评论（默认不限）。

requireFieldsarray

editedisAuthor

Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `edited` or `isAuthor`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a comment that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.

import os, requests

res = requests.post(
    "https://api.getanyapi.com/v1/run/linkedin.profile_comments",
    headers={"Authorization": f"Bearer {os.environ['ANYAPI_KEY']}"},
    json={
        "url": "https://www.linkedin.com/in/jeffweiner08",
        "limit": 10
    },
)
print(res.json())

const res = await fetch("https://api.getanyapi.com/v1/run/linkedin.profile_comments", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.ANYAPI_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "url": "https://www.linkedin.com/in/jeffweiner08",
    "limit": 10
  }),
});
const data = await res.json();
console.log(data);

curl -X POST https://api.getanyapi.com/v1/run/linkedin.profile_comments \
  -H "Authorization: Bearer $ANYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://www.linkedin.com/in/jeffweiner08","limit":10}'

打开于提示词已复制

获取免费密钥

示例响应

免费运行只返回前 3 条结果。为密钥充值即可获得完整响应。

这个示例展示了 36 个字段中的 35 个。查看全部字段

{
  "found": true,
  "data": {
    "items": [
      {
        "id": "urn:li:comment:(urn:li:activity:7481203945521098752,7481204988612345601)",
        "commentary": "This matches what we are seeing across our portfolio too. The teams that treat AI adoption as a workflow redesign problem, not a tooling purchase, are the ones pulling ahead.",
        "url": "https://www.linkedin.com/feed/update/urn:li:activity:7481203945521098752?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7481203945521098752%2C7481204988612345601%29",
        "createdUtc": 1758470400,
        "edited": false,
        "isAuthor": false,
        "actor": {
          "id": "ACoAAB1kQnRp8sTwYxV4mL2oZ7cN3bE9dJrK6fA",
          "name": "Jeff Weiner",
          "type": "profile",
          "linkedinUrl": "https://www.linkedin.com/in/jeffweiner08",
          "position": "Executive Chairman at LinkedIn",
          "image": "https://media.licdn.com/dms/image/v2/D4E03AQCz9nRk2wLpXm/profile-displayphoto-shrink_400_400/jeff-weiner.jpg"
        },
        "engagement": {
          "likes": 214,
          "comments": 6,
          "shares": 0
        },
        "post": {
          "id": "urn:li:activity:7481203945521098752",
          "url": "https://www.linkedin.com/feed/update/urn:li:activity:7481203945521098752",
          "text": "New data from our workplace learning survey: companies that redesigned at least one core workflow around AI this year saw 3x the productivity lift of those that only added a chat assistant on top of existing processes.",
          "postedUtc": 1758440400,
          "author": {
            "name": "Aisha Kapoor",
            "headline": "VP of Learning and Development at Meridian Health",
            "profileUrl": "https://www.linkedin.com/in/aisha-kapoor-ld",
            "publicIdentifier": "aisha-kapoor-ld",
            "image": "https://media.licdn.com/dms/image/v2/D4E03AQFp7nWkRz2xTd/profile-displayphoto-shrink_400_400/aisha-kapoor.jpg"
          },
          "engagement": {
            "reactions": 3820,
            "comments": 142,
            "reposts": 96
          }
        }
      },
      {
        "id": "urn:li:comment:(urn:li:activity:7480117620987654321,7480118872341987602)",
        "commentary": "Congrats on the launch. Curious how you are handling attribution when a candidate applies through both the careers page and a referral link in the same week.",
        "url": "https://www.linkedin.com/feed/update/urn:li:activity:7480117620987654321?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7480117620987654321%2C7480118872341987602%29",
        "createdUtc": 1758300000,
        "edited": true,
        "isAuthor": false,
        "actor": {
          "id": "ACoAAB1kQnRp8sTwYxV4mL2oZ7cN3bE9dJrK6fA",
          "name": "Jeff Weiner",
          "type": "profile",
          "linkedinUrl": "https://www.linkedin.com/in/jeffweiner08",
          "position": "Executive Chairman at LinkedIn",
          "image": "https://media.licdn.com/dms/image/v2/D4E03AQCz9nRk2wLpXm/profile-displayphoto-shrink_400_400/jeff-weiner.jpg"
        },
        "engagement": {
          "likes": 38,
          "comments": 2,
          "shares": 0
        },
        "post": {
          "id": "urn:li:activity:7480117620987654321",
          "url": "https://www.linkedin.com/feed/update/urn:li:activity:7480117620987654321",
          "text": "We just shipped referral tracking that follows a candidate across every entry point, from a shared job link to an inbound application, so recruiters see one unified timeline.",
          "postedUtc": 1758280800,
          "author": {
            "name": "Marcus Oyelaran",
            "headline": "Head of Product, Talent Solutions at Brightloop",
            "profileUrl": "https://www.linkedin.com/in/marcus-oyelaran",
            "publicIdentifier": "marcus-oyelaran",
            "image": "https://media.licdn.com/dms/image/v2/D4E03AQJt2mWkLp8vRz/profile-displayphoto-shrink_400_400/marcus-oyelaran.jpg"
          },
          "engagement": {
            "reactions": 512,
            "comments": 34,
            "reposts": 11
          }
        }
      }
    ]
  }
}

完整的参数与响应参考：这个接口的每个字段、类型和示例。

参考

一个请求，一种响应结构。

你发送的每个字段和收到的每个字段，都附有真实示例。

最近验证于 2026-11-14 · 可用率和延迟按 30d 统计

请求体

JSON，POST 到这个接口。

urlstring
https://www.linkedin.com/in/jeffweiner08
要列出其在他人帖子下评论的 LinkedIn 会员主页完整 URL。
limitinteger
10
最多返回的评论数。
postedLimitenum
只返回在此时间范围内发布的评论（默认不限）。
requireFieldsarray
Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `edited` or `isAuthor`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a comment that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.

你发送。 一个简短的 JSON 请求体。显示的值只是示例，请换成你自己的。

响应

JSON，每个字段一个示例值。

actordata.items[].actor

The member who left the comment (a profile or a company).

idstring
ACoAAB1kQnRp8sTwYxV4mL2oZ7cN3bE9dJrK6fA
LinkedIn identifier of the commenter.
imagestring
https://media.licdn.com/dms/image/v2/D4E03AQCz9nRk2wLpXm/profile-displayphoto-shrink_400_400/jeff-weiner.jpg
Profile picture URL of the commenter. Populated whenever the provider has data for the entity.
linkedinUrlstring
https://www.linkedin.com/in/jeffweiner08
Canonical LinkedIn URL of the commenter. Populated whenever the provider has data for the entity.
namestring
Jeff Weiner
Display name of the commenter. Populated whenever the provider has data for the entity.
positionstring
Executive Chairman at LinkedIn
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'.

each itemdata.items[]

Comments this member left on other people's posts, newest first, each with the post it was left on. Populated whenever the provider has data for the entity.

commentarystring
This matches what we are seeing across our portfolio too. The teams that treat AI adoption as a workflow redesign problem, not a tooling purchase, are the ones pulling ahead.
Full text of the comment the member left. Populated whenever the provider has data for the entity.
createdUtcnumber
1758470400
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. Null when the serving source does not report it.
idstring
urn:li:comment:(urn:li:activity:7481203945521098752,7481204988612345601)
Unique identifier of the comment. Populated whenever the provider has data for the entity.
isAuthorboolean可设为必填
false
Whether the commenter is also the author of the post. Null when the serving source does not report it.
urlstring
https://www.linkedin.com/feed/update/urn:li:activity:7481203945521098752?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7481203945521098752%2C7481204988612345601%29
Canonical permalink URL of the comment. Populated whenever the provider has data for the entity.

engagementdata.items[].engagement

Engagement metrics for the comment.

commentsinteger
6
Number of replies to the comment.
likesinteger
214
Number of likes on the comment.
sharesinteger
0
Number of shares of the comment.

authordata.items[].post.author

Author of the post that was commented on.

headlinestring
VP of Learning and Development at Meridian Health
Public headline or company follower summary for the post author.
imagestring
https://media.licdn.com/dms/image/v2/D4E03AQFp7nWkRz2xTd/profile-displayphoto-shrink_400_400/aisha-kapoor.jpg
Profile or company image URL of the post author. Populated whenever the provider has data for the entity.
namestring
Aisha Kapoor
Display name of the post author. Populated whenever the provider has data for the entity.
profileUrlstring
https://www.linkedin.com/in/aisha-kapoor-ld
Canonical LinkedIn profile or company URL of the post author. Populated whenever the provider has data for the entity.
publicIdentifierstring
aisha-kapoor-ld
LinkedIn public identifier (vanity slug) of the post author, for example "williamhgates". Stable across lanes, unlike the raw id.

engagementdata.items[].post.engagement

Public engagement totals on the post that was commented on.

commentsinteger
142
Total comment count on the post.
reactionsinteger
3820
Total reaction count on the post.
repostsinteger
96
Total repost or share count on the post.

postdata.items[].post

The post the comment was left on, so the comment can be read in context. Populated whenever the provider has data for the entity.

idstring
urn:li:activity:7481203945521098752
Unique identifier of the LinkedIn post that was commented on.
postedUtcnumber
1758440400
UTC epoch timestamp in seconds (Unix time) when the post was published. Multiply by 1000 for a JS Date in milliseconds. Populated whenever the provider has data for the entity.
textstring
New data from our workplace learning survey: companies that redesigned at least one core workflow around AI this year saw 3x the productivity lift of those that only added a chat assistant on top of existing processes.
Text content of the post that was commented on. Empty when the post carries no commentary of its own, such as a bare reshare or an image-only post. Populated whenever the provider has data for the entity.
urlstring
https://www.linkedin.com/feed/update/urn:li:activity:7481203945521098752
Canonical LinkedIn URL of the post that was commented on. Populated whenever the provider has data for the entity.

top level

foundboolean
true
Whether comments by this member were found.
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.profile_comments，就以统一格式的 JSON 返回 LinkedIn 数据。列出某个 LinkedIn 会员在他人帖子下留下的评论：评论正文、永久链接和时间戳，以及所评论的帖子、该帖子的作者和互动数据。AnyAPI 会在 2 个数据源之间路由每个请求，某个数据源失败时自动切换。费用：每千次请求 US$2.90 起，以美元计价，无需订阅，也没有每月最低消费。过去 30 天，通过 AnyAPI 发起的 LinkedIn 主页评论 API 调用中有 100.0% 成功，响应时间中位数为 3.7 秒，共测量 5,021 次调用。

费用：每千次请求 US$2.90 起，以美元计价，无需订阅，也没有每月最低消费。你只需为一个美元钱包充值，每次调用从中扣费。部分由钱包付费的失败请求会产生处理费用，我们按成本原价转嫁，不加价；错误响应会显示收取的金额。

列出某个 LinkedIn 会员在他人帖子下留下的评论：评论正文、永久链接和时间戳，以及所评论的帖子、该帖子的作者和互动数据。响应是统一格式的 JSON，外层结构与每个 AnyAPI 接口相同，所以解析另一个接口只需换一个 URL，别的都不用改。

过去 30 天，通过 AnyAPI 发起的 LinkedIn 主页评论 API 调用中有 100.0% 成功，响应时间中位数为 3.7 秒，共测量 5,021 次调用。这些是 AnyAPI 对经过网关的流量的自有测量，持续重新计算，并非公开承诺的服务等级目标。

可以。新的 AnyAPI 账户自带 US$0.10 免费余额，无需绑卡，足够调用 34 次 LinkedIn 主页评论，每次 US$0.0029。

AnyAPI 会在同一个请求中依次尝试它的 2 个数据源，从最便宜的开始，所以一个数据源宕机不会让你的调用失败。

向 https://api.getanyapi.com/v1/run/linkedin.profile_comments 发送 POST 请求，在 “Authorization: Bearer” 请求头中放入你的 AnyAPI 密钥，并以 JSON 请求体传入参数。同一个密钥和同一个钱包适用于所有 AnyAPI 接口。

不需要。你向一个预付费的 AnyAPI 余额充值美元，每个请求从中扣费。没有月度套餐，也没有最低消费，同一个余额可用于所有 AnyAPI 接口。

有。TypeScript 用 npm 安装 @getanyapi/sdk，Python 用 pip 安装 getanyapi。两者都用同一个密钥调用所有 AnyAPI 接口，任何 HTTP 客户端也都可以。

可以。智能体可以连接 https://api.getanyapi.com/mcp 上的 AnyAPI MCP 服务器，或者向 https://api.getanyapi.com/agent/signup 发送一次无需认证的 POST 来创建自己的免费试用密钥，再通过 HTTP 调用这个接口。

更多接口

LinkedIn 的其他接口

一个密钥，一个钱包，
开始你的第一次 LinkedIn 调用。

领取 ~160 次免费请求

LinkedIn 主页评论 API

Jeff Weiner's Activity

LinkedIn 主页评论 API 价格：一个 API，2 个可互换的服务商

一个请求获取 LinkedIn 主页评论

一个请求，一种响应结构。

关于 LinkedIn 主页评论 API

LinkedIn 主页评论 API 怎么收费？

LinkedIn 主页评论 API 返回什么？

LinkedIn 主页评论 API 的可靠性如何？

LinkedIn 主页评论 API 可以免费试用吗？

LinkedIn 主页评论 API 的某个数据源失败时会怎样？

如何调用 LinkedIn 主页评论 API？

使用 LinkedIn 主页评论 API 需要订阅吗？

LinkedIn 主页评论 API 有 SDK 吗？

AI 智能体可以使用 LinkedIn 主页评论 API 吗？

LinkedIn 的其他接口

一个密钥，一个钱包，开始你的第一次 LinkedIn 调用。

一个密钥，一个钱包，
开始你的第一次 LinkedIn 调用。