LinkedIn API

LinkedIn 帖子评论 API

列出 LinkedIn 帖子下的评论:完整正文、评论者姓名/URL/职位、时间戳和互动数据。

POST/v1/run/linkedin.post_comments
可用率
100.00%
30d · 885 次调用
请求数
885
30d · 按周,近 12 周
响应时间
2.0s
中位数 · 30d

试一试

发出你的第一个请求

打开于
获取免费密钥
示例响应
免费运行只返回前 3 条结果。为密钥充值即可获得完整响应。
{
  "data": {
    "items": [
      {
        "actor": {
          "id": "a1b2c3d4",
          "image": "https://example.com/image.jpg",
          "linkedinUrl": "https://example.com/page",
          "name": "Example title",
          "position": "example",
          "type": "general"
        },
        "commentary": "example",
        "createdUtc": 12.5,
        "edited": true,
        "engagement": {
          "comments": 12500,
          "likes": 12500
        },
        "id": "a1b2c3d4",
        "pinned": true,
        "url": "https://example.com/page"
      }
    ]
  },
  "found": true,
  "reason": "not_found"
}
响应类型定义
interface LinkedinPostCommentsResponse {
  data: {
    items: {
      actor?: {
        id?: string;
        image?: string;
        linkedinUrl?: string;
        name?: string;
        position?: string;
        type?: string;
      };
      commentary: string;
      createdUtc?: number;
      edited?: boolean;
      engagement?: {
        comments?: number;
        likes?: number;
      };
      id: string;
      pinned?: boolean;
      url?: string;
    }[];
  } | null;
  found: boolean;
  reason?: "not_found";
}

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

参考

请求、响应与价格

最近验证于 2026-09-29 · 可用率和延迟按 30d 统计
POST /v1/run/linkedin.post_comments
curl -X POST https://api.getanyapi.com/v1/run/linkedin.post_comments \
  -H "Authorization: Bearer $ANYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"limit":10,"url":"https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ"}'
字段类型示例值
请求体
urlstring"https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ"要列出评论的 LinkedIn 帖子完整 URL。
limitinteger10最多返回的评论数。
postedLimitenum只返回在此时间范围内发布的评论(默认不限)。
响应
dataobjectThe post comments result, or null when not found.
data.itemsobject[]The post's comments. Populated whenever the provider has data for the entity.
data.items[].actorobjectThe commenter (a profile or a company).
data.items[].actor.idstringLinkedIn identifier of the commenter.
data.items[].actor.imagestringProfile picture URL of the commenter. Populated whenever the provider has data for the entity.
data.items[].actor.linkedinUrlstringCanonical LinkedIn URL of the commenter. Populated whenever the provider has data for the entity.
data.items[].actor.namestringDisplay name of the commenter. Populated whenever the provider has data for the entity.
data.items[].actor.positionstringCommenter's headline or job title as displayed. Populated whenever the provider has data for the entity.
data.items[].actor.typestringCommenter kind, e.g. 'profile' or 'company'.
data.items[].commentarystringFull text of the comment. Populated whenever the provider has data for the entity.
data.items[].createdUtcnumberUTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds. Populated whenever the provider has data for the entity.
data.items[].editedbooleanWhether the comment has been edited.
data.items[].engagementobjectEngagement metrics for the comment.
data.items[].engagement.commentsintegerNumber of replies to the comment.
data.items[].engagement.likesintegerNumber of likes on the comment.
data.items[].idstringUnique identifier of the comment. Populated whenever the provider has data for the entity.
data.items[].pinnedbooleanWhether the comment is pinned on the post.
data.items[].urlstringCanonical permalink URL of the comment. Populated whenever the provider has data for the entity.
foundbooleanWhether 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.
价格
每次请求价格USDUS$0.005
价格(/千次请求)USDUS$5.00

常见问题

关于 LinkedIn 帖子评论 API

AnyAPI 的 LinkedIn 帖子评论 API 只需一次 POST 请求 /v1/run/linkedin.post_comments,就以统一格式的 JSON 返回 LinkedIn 数据。列出 LinkedIn 帖子下的评论:完整正文、评论者姓名/URL/职位、时间戳和互动数据。AnyAPI 会在 3 个数据源之间路由每个请求,某个数据源失败时自动切换。费用:每千次请求 US$5 起,以美元计价,无需订阅,也没有每月最低消费。过去 30 天,通过 AnyAPI 发起的 LinkedIn 帖子评论 API 调用中有 100.0% 成功,响应时间中位数为 2.0 秒,共测量 885 次调用。

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

列出 LinkedIn 帖子下的评论:完整正文、评论者姓名/URL/职位、时间戳和互动数据。响应是统一格式的 JSON,外层结构与每个 AnyAPI 接口相同,所以解析另一个接口只需换一个 URL,别的都不用改。

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