LinkedIn API

LinkedIn 主页反应 API

列出某个 LinkedIn 会员做出过反应的帖子:反应、时间戳,以及所反应的完整帖子及其作者和互动数据。

POST/v1/run/linkedin.profile_reactions
可用率
100.00%
30d · 3 次调用
请求数
3
30d
响应时间
2.6s
中位数 · 30d

价格

一个价格,以美元计

试一试

发出你的第一个请求

打开于
获取免费密钥
示例响应
免费运行只返回前 3 条结果。为密钥充值即可获得完整响应。
{
  "data": {
    "items": [
      {
        "action": "example",
        "actor": {
          "id": "a1b2c3d4",
          "image": "https://example.com/image.jpg",
          "linkedinUrl": "https://example.com/page"
        },
        "createdUtc": 12.5,
        "id": "a1b2c3d4",
        "post": {
          "author": {
            "headline": "Example title",
            "id": "a1b2c3d4",
            "image": "https://example.com/image.jpg",
            "name": "Example title",
            "profileUrl": "https://example.com/page",
            "publicIdentifier": "a1b2c3d4",
            "type": "general",
            "universalName": "Example title"
          },
          "engagement": {
            "breakdown": [
              null
            ],
            "comments": 12500,
            "reactions": 42,
            "reposts": 248
          },
          "id": "a1b2c3d4",
          "postedUtc": 248,
          "repostId": "a1b2c3d4",
          "text": "A short example description of this item.",
          "url": "https://example.com/page"
        },
        "url": "https://example.com/page"
      }
    ]
  },
  "found": true,
  "reason": "not_found"
}
响应类型定义
interface LinkedinProfileReactionsResponse {
  data: {
    items: {
      action: string;
      actor?: {
        id?: string;
        image?: string;
        linkedinUrl?: string;
      };
      createdUtc?: number;
      id: string;
      post?: {
        author?: {
          headline?: string;
          id?: string;
          image?: string;
          name?: string;
          profileUrl?: string;
          publicIdentifier?: string;
          type?: string;
          universalName?: string;
        };
        engagement?: {
          breakdown?: {
            count: number;
            type: string;
          }[];
          comments?: number;
          reactions?: number;
          reposts?: number;
        };
        id?: string;
        postedUtc?: number;
        repostId?: string;
        text?: string;
        url?: string;
      };
      url?: string;
    }[];
  } | null;
  found: boolean;
  reason?: "not_found";
}

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

参考

请求、响应与价格

最近验证于 2026-09-29 · 可用率和延迟按 30d 统计
POST /v1/run/linkedin.profile_reactions
curl -X POST https://api.getanyapi.com/v1/run/linkedin.profile_reactions \
  -H "Authorization: Bearer $ANYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"limit":10,"url":"https://www.linkedin.com/in/williamhgates"}'
字段类型示例值
请求体
urlstring"https://www.linkedin.com/in/williamhgates"要列出其反应的 LinkedIn 会员主页完整 URL,例如 https://www.linkedin.com/in/williamhgates。
limitinteger10最多返回的反应数。一个上游页面包含 100 条。
响应
dataobjectThe profile reactions result, or null when not found.
data.itemsobject[]Posts the member has reacted to, newest first. One record per reaction, carrying both the reaction itself and the post it was made on. Populated whenever the provider has data for the entity.
data.items[].actionstringLinkedIn's own display sentence for the reaction, for example "Bill Gates likes this" or "Ali Abdaal liked Tobi Odutola's comment on this". It is the only place the reaction kind appears on this endpoint, it names the member and sometimes a third party, and it distinguishes a reaction on the post from a reaction on a comment. It is free English text, not an enum: parse it only if you accept that LinkedIn may reword it. Populated whenever the provider has data for the entity.
data.items[].actorobjectThe member who reacted - the profile that was asked about. Populated whenever the provider has data for the entity.
data.items[].actor.idstringLinkedIn member identifier of the reactor.
data.items[].actor.imagestringProfile picture URL of the reactor.
data.items[].actor.linkedinUrlstringCanonical LinkedIn profile URL of the reactor. 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[].idstringLinkedIn activity identifier of the reaction event itself. This is not the identifier of the post that was reacted to - that is post.id. Populated whenever the provider has data for the entity.
data.items[].postobjectThe post the member reacted to. Populated whenever the provider has data for the entity.
data.items[].post.authorobjectPublic author identity attached to the post. Populated whenever the provider has data for the entity.
data.items[].post.author.headlinestringPublic headline for a person, or the follower summary for a company. Populated whenever the provider has data for the entity.
data.items[].post.author.idstringLinkedIn identifier for the author.
data.items[].post.author.imagestringPublic profile or company image URL for the author.
data.items[].post.author.namestringDisplay name of the author. Populated whenever the provider has data for the entity.
data.items[].post.author.profileUrlstringCanonical LinkedIn profile or company URL for the author. Populated whenever the provider has data for the entity.
data.items[].post.author.publicIdentifierstringLinkedIn public identifier (vanity slug) for the author, for example "williamhgates". Absent for company authors, which carry universalName instead.
data.items[].post.author.typestringAuthor kind, such as profile or company.
data.items[].post.author.universalNamestringUniversal LinkedIn name used for company authors, when present.
data.items[].post.engagementobjectPublic engagement totals attached to the post. Populated whenever the provider has data for the entity.
data.items[].post.engagement.breakdownobject[]Reaction counts on the post grouped by LinkedIn reaction type.
data.items[].post.engagement.breakdown[].countintegerNumber of reactions of this type.
data.items[].post.engagement.breakdown[].typestringLinkedIn reaction type.
data.items[].post.engagement.commentsintegerTotal comment count.
data.items[].post.engagement.reactionsintegerTotal reaction count.
data.items[].post.engagement.repostsintegerTotal repost or share count.
data.items[].post.idstringLinkedIn activity identifier of the post that was reacted to. Populated whenever the provider has data for the entity.
data.items[].post.postedUtcnumberUTC epoch timestamp in seconds (Unix time) the post was published. Multiply by 1000 for a JS Date in milliseconds.
data.items[].post.repostIdstringUnique identifier of the post this one reshares, when it is a reshare.
data.items[].post.textstringText content of the post. Empty string 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.
data.items[].post.urlstringCanonical LinkedIn URL of the post. Populated whenever the provider has data for the entity.
data.items[].urlstringCanonical LinkedIn feed URL of the reaction event. Use post.url for the post itself. Populated whenever the provider has data for the entity.
foundbooleanWhether reactions were found for the profile.
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.profile_reactions,就以统一格式的 JSON 返回 LinkedIn 数据。列出某个 LinkedIn 会员做出过反应的帖子:反应、时间戳,以及所反应的完整帖子及其作者和互动数据。无论哪个数据源提供服务,AnyAPI 都返回同一套统一的 schema。费用:每千次请求 US$5 起,以美元计价,无需订阅,也没有每月最低消费。过去 30 天,通过 AnyAPI 发起的 LinkedIn 主页反应 API 调用中有 100.0% 成功,响应时间中位数为 2.6 秒,共测量 3 次调用。

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

列出某个 LinkedIn 会员做出过反应的帖子:反应、时间戳,以及所反应的完整帖子及其作者和互动数据。响应是统一格式的 JSON,外层结构与每个 AnyAPI 接口相同,所以解析另一个接口只需换一个 URL,别的都不用改。

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