LinkedIn API
LinkedIn 搜索帖子(完整版) API
搜索公开的 LinkedIn 帖子,附带丰富的作者、互动、附件和投票详情。
POST/v1/run/linkedin.search_posts_full
可用率
100.00%
30d · 5,001 次调用
请求数
5,007
30d · 按周,近 12 周
响应时间
3.2s
中位数 · 30d
服务商网络
按流量排序的服务商
服务商
每次请求封顶 US$0.1431 条结果US$0.0014350 条结果US$0.0715100 条结果US$0.143(封顶)按实际返回的内容计费。调低返回数量上限即可少付,而且无论返回多少,单次请求都不会超过封顶价。
每次请求封顶 US$0.1941 条结果US$0.0030950 条结果US$0.09766100 条结果US$0.194(封顶)按实际返回的内容计费。调低返回数量上限即可少付,而且无论返回多少,单次请求都不会超过封顶价。
试一试
发出你的第一个请求
requireFieldsarray可选;省略时路由不变,由最便宜的数据源处理。列出本次请求必须能返回的输出字段,例如 `attachmentType` 或 `pollOptions`,请求就只会由能返回全部这些字段的数据源处理。未列出的字段,只要处理请求的数据源有,仍会照常返回。这可能提高你的价格:最便宜的数据源无法返回某个列出的字段时,会改由更贵的数据源处理,并按它的价格报价和扣费。如果某条帖子确实没有某个列出的字段,该字段仍可能缺失。如果列出的字段组合没有任何单一数据源能同时返回,请求会作为无效输入被拒绝,不扣费。
示例响应
免费运行只返回前 3 条结果。为密钥充值即可获得完整响应。
{
"data": {
"posts": [
{
"attachmentDescription": "A short example description of this item.",
"attachmentImage": "https://example.com/image.jpg",
"attachmentSubtitle": "Example title",
"attachmentTitle": "Example title",
"attachmentType": "general",
"attachmentUrl": "https://example.com/page",
"author": {
"headline": "Example title",
"id": "a1b2c3d4",
"image": "https://example.com/image.jpg",
"name": "Example title",
"profileUrl": "https://example.com/page",
"publicIdentifier": "a1b2c3d4",
"type": "person"
},
"createdUtc": 12.5,
"engagement": {
"breakdown": [
{
"count": null,
"type": null
}
],
"comments": 12500,
"reactions": 42,
"reposts": 248
},
"id": "a1b2c3d4",
"pollClosed": false,
"pollOptions": [
{
"text": "A short example description of this item.",
"votes": 42
}
],
"pollQuestion": "example",
"pollTotalVotes": 12500,
"text": "A short example description of this item.",
"url": "https://example.com/page"
}
]
},
"found": true,
"reason": "not_found"
}响应类型定义
interface LinkedinSearchPostsFullResponse {
data: {
posts: {
attachmentDescription?: string;
attachmentImage?: string;
attachmentSubtitle?: string;
attachmentTitle?: string;
attachmentType?: string;
attachmentUrl?: string;
author: {
headline?: string;
id?: string;
image?: string;
name?: string;
profileUrl?: string;
publicIdentifier?: string;
type?: "person" | "company" | "showcase";
};
createdUtc: number;
engagement: {
breakdown?: {
count: number;
type: string;
}[];
comments?: number;
reactions?: number;
reposts?: number;
};
id: string;
pollClosed?: boolean;
pollOptions?: {
text: string;
votes: number;
}[];
pollQuestion?: string;
pollTotalVotes?: number;
text: string;
url: string;
}[];
} | null;
found: boolean;
reason?: "not_found";
}完整的参数与响应参考:这个接口的每个字段、类型和示例。
参考
请求、响应与价格
最近验证于 2026-09-29 · 可用率和延迟按 30d 统计POST /v1/run/linkedin.search_posts_full
curl -X POST https://api.getanyapi.com/v1/run/linkedin.search_posts_full \
-H "Authorization: Bearer $ANYAPI_KEY" \
-H "Content-Type: application/json" \
-d '{"datePosted":"last-week","limit":10,"query":"artificial intelligence","sort":"relevance"}'| 字段 | 类型 | 示例值 |
|---|---|---|
| 请求体 | ||
| query | string | "artificial intelligence"LinkedIn 帖子搜索查询,可包含 LinkedIn 搜索支持的带引号词语或布尔运算符。 |
| authorCompanyNames | array | 只返回与这些公司名称相关的人员发布的帖子。 |
| authorIndustryIds | array | 只返回与这些 LinkedIn 行业 ID 相关的作者发布的帖子。 |
| authorKeywords | string | 只返回作者主页头衔或职位名称中至少包含其中一个关键词的帖子。 |
| authorUrls | array | 只返回由这些 LinkedIn 主页或公司 URL 发布的帖子。 |
| contentType | enum | 只返回带有此内容类型的帖子。 |
| datePosted | enum | "last-week"只返回在此相对时间范围内发布的帖子。过去一小时以及超过一个月的时间范围会路由到支持它们的服务商。 |
| limit | integer | 10最多返回的帖子数(1-100,默认 10)。上限为一页 LinkedIn 搜索结果。 |
| mentioningMemberUrls | array | 只返回提及这些 LinkedIn 会员主页 URL 的帖子。 |
| requireFields | array | 可选;省略时路由不变,由最便宜的数据源处理。列出本次请求必须能返回的输出字段,例如 `attachmentType` 或 `pollOptions`,请求就只会由能返回全部这些字段的数据源处理。未列出的字段,只要处理请求的数据源有,仍会照常返回。这可能提高你的价格:最便宜的数据源无法返回某个列出的字段时,会改由更贵的数据源处理,并按它的价格报价和扣费。如果某条帖子确实没有某个列出的字段,该字段仍可能缺失。如果列出的字段组合没有任何单一数据源能同时返回,请求会作为无效输入被拒绝,不扣费。 |
| sort | enum | "relevance"按搜索相关性或发布日期对结果排序。 |
| 响应 | ||
| data | object | The matching LinkedIn posts, or null when no result was found. |
| data.posts | object[] | LinkedIn posts matching the search query. Populated whenever the provider has data for the entity. |
| data.posts[].attachmentDescription可设为必填 | string | Short description of the attached content, as LinkedIn shows it on the preview card. Best effort on article attachments: depending on the search it may be absent, so treat it as optional. To read an article's content reliably, pass attachmentUrl to the linkedin.article endpoint. |
| data.posts[].attachmentImage可设为必填 | string | Image URL associated with the attachment. |
| data.posts[].attachmentSubtitle可设为必填 | string | Subtitle of the attached structured content. |
| data.posts[].attachmentTitle可设为必填 | string | Title of the attached article, job, or other structured content. |
| data.posts[].attachmentType可设为必填 | string | Kind of structured content attached to the post, such as article, job, poll, video, or document. |
| data.posts[].attachmentUrl可设为必填 | string | Canonical destination URL of the attachment. When attachmentType is article, pass this URL to the linkedin.article endpoint to read the article's full body text. |
| data.posts[].author | object | Public author identity attached to the post. Populated whenever the provider has data for the entity. |
| data.posts[].author.headline | string | Public headline or company follower summary for the author. |
| data.posts[].author.id | string | LinkedIn identifier for the author. |
| data.posts[].author.image | string | Public profile or company image URL for the author. |
| data.posts[].author.name | string | Display name of the author. |
| data.posts[].author.profileUrl | string | Canonical LinkedIn profile or company URL for the author. |
| data.posts[].author.publicIdentifier | string | LinkedIn public identifier (vanity slug) for the author, for example "williamhgates". Stable across lanes, unlike the raw id. |
| data.posts[].author.type | "person" | "company" | "showcase" | Kind of LinkedIn entity that authored the post, derived from the author URL. |
| data.posts[].createdUtc | number | 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. |
| data.posts[].engagement | object | Public engagement totals attached to the post. Populated whenever the provider has data for the entity. |
| data.posts[].engagement.breakdown | object[] | Reaction counts grouped by LinkedIn reaction type. |
| data.posts[].engagement.breakdown[].count | integer | Number of reactions of this type. |
| data.posts[].engagement.breakdown[].type | string | LinkedIn reaction type. |
| data.posts[].engagement.comments | integer | Total comment count. |
| data.posts[].engagement.reactions | integer | Total reaction count. |
| data.posts[].engagement.reposts | integer | Total repost or share count. |
| data.posts[].id | string | Stable LinkedIn activity identifier for the post. Populated whenever the provider has data for the entity. |
| data.posts[].pollClosed可设为必填 | boolean | Whether the attached poll is closed. |
| data.posts[].pollOptions可设为必填 | object[] | Options and public vote counts for an attached poll. |
| data.posts[].pollOptions[].text | string | Poll option text. |
| data.posts[].pollOptions[].votes | integer | Votes recorded for this option. |
| data.posts[].pollQuestion可设为必填 | string | Question asked by an attached LinkedIn poll. |
| data.posts[].pollTotalVotes可设为必填 | integer | Total votes recorded by the attached poll. |
| data.posts[].text | string | Text content of the post. Empty string when the post carries no commentary of its own, such as a bare article share or an image-only post. Populated whenever the provider has data for the entity. |
| data.posts[].url | string | Canonical URL of the LinkedIn post. Populated whenever the provider has data for the entity. |
| found | boolean | Whether matching LinkedIn posts 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. |
| 价格 | ||
| 每次请求价格 | USD | US$0.004 |
| 价格(/千次请求) | USD | US$4.00 |
常见问题
关于 LinkedIn 搜索帖子(完整版) API
AnyAPI 的 LinkedIn 搜索帖子(完整版) API 只需一次 POST 请求 /v1/run/linkedin.search_posts_full,就以统一格式的 JSON 返回 LinkedIn 数据。搜索公开的 LinkedIn 帖子,附带丰富的作者、互动、附件和投票详情。AnyAPI 会在 4 个数据源之间路由每个请求,某个数据源失败时自动切换。费用:每千次请求 US$4 起,以美元计价,无需订阅,也没有每月最低消费。过去 30 天,通过 AnyAPI 发起的 LinkedIn 搜索帖子(完整版) API 调用中有 100.0% 成功,响应时间中位数为 3.2 秒,共测量 5,001 次调用。
费用:每千次请求 US$4 起,以美元计价,无需订阅,也没有每月最低消费。你只需为一个美元钱包充值,每次调用从中扣费。部分由钱包付费的失败请求会产生处理费用,我们按成本原价转嫁,不加价;错误响应会显示收取的金额。
搜索公开的 LinkedIn 帖子,附带丰富的作者、互动、附件和投票详情。响应是统一格式的 JSON,外层结构与每个 AnyAPI 接口相同,所以解析另一个接口只需换一个 URL,别的都不用改。
过去 30 天,通过 AnyAPI 发起的 LinkedIn 搜索帖子(完整版) API 调用中有 100.0% 成功,响应时间中位数为 3.2 秒,共测量 5,001 次调用。这些是 AnyAPI 对经过网关的流量的自有测量,持续重新计算,并非公开承诺的服务等级目标。
更多接口
LinkedIn 的其他接口
主页/千次请求 US$2.90 起公司/千次请求 US$1.10 起公司帖子/千次请求 US$5.00 起帖子/千次请求 US$0.50 起帖子搜索/千次请求 US$1.20 起广告/千次请求 US$1.20 起广告列表/千条结果 US$1.58 起广告搜索/千次请求 US$1.20 起文章/千次请求 US$5.69 起公司员工/千次请求 US$6.00 起公司帖子(精简版)/千次请求 US$1.20 起公司(精简版)/千次请求 US$1.00 起邮箱/千次请求 US$11.00 起职位/千次请求 US$1.50 起职位/千条结果 US$1.14 起职位(精简版)/千次请求 US$0.50 起帖子评论/千次请求 US$5.00 起帖子反应/千次请求 US$2.90 起帖子转录文本/千次请求 US$1.20 起主页评论/千次请求 US$5.00 起主页帖子(完整版)/千次请求 US$5.00 起主页帖子(精简版)/千次请求 US$5.00 起主页反应/千次请求 US$5.00 起主页(精简版)/千次请求 US$0.80 起搜索公司/千次请求 US$5.00 起搜索主页/千条结果 US$7.92 起搜索主页(含邮箱)/千条结果 US$12.92 起搜索主页(精简版)/千次请求 US$36.00 起