LinkedIn API

LinkedIn 文章 API

按 URL 读取公开的 LinkedIn 文章或新闻通讯期刊,包括完整正文、作者、发布时间和互动数据。

US$5.65/千次请求,按请求付费,无需订阅。

in(1) Why most forecasting models fail in the second quarter | LinkedIn
linkedin.com/pulse/why-most-forecasting-models-fail-quarter-two-daniela-ruiz

Why most forecasting models fail in the second quarter

Daniela Ruiz

Published August 22, 2025

Suppose your forecast is built on last January's demand curve. By April, the assumptions underneath it have already moved twice.

612 · 47 Comments
LikeCommentShare

Others also viewed

API 返回的内容
{
"url": "https://www.linkedin.com/pulse/why-most-forecasting-models-fail-quarter-two-daniela-ruiz",
"title": "Why most forecasting models fail in the second quarter",
"body": "Suppose your forecast is built on last January's demand curve. By April, the assumptions underneath it have already moved twice.\n\nMost finance teams do not notice until the variance report lands, and by then the quarter is half over. The fix is not a better model. It is a shorter feedback loop between the actuals and the assumptions that produced the forecast.\n\nOver the last year we worked with a dozen mid-market finance teams rebuilding this loop. Three changes showed up in every team that closed its variance gap: weekly actuals instead of monthly, a single owner per assumption, and a standing fifteen minute review that only asks what changed.\n\nNone of this requires new tooling. It requires treating the forecast as a living document instead of a quarterly artifact.",
"description": "Three changes that closed the variance gap for a dozen finance teams, and none of them required new software.",
"author": "Daniela Ruiz",
"authorUrl": "https://www.linkedin.com/in/daniela-ruiz-fpa",
"authorFollowers": 18400,
"createdUtc": 1755878400,
... 还有 5 个字段
}
可用率
93.02%
30d · 215 次调用
请求数
215
30d · 按周,近 12 周
响应时间
4.5s
中位数 · 30d

价格

LinkedIn 文章 API 价格

你需支付
US$56.50
US$5.65/千次请求,只为实际用量付费。没有月度套餐。
有了 US$0.10 的初始余额,你的前 17 次请求免费。

试一试

一个请求获取 LinkedIn 文章

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

这个示例展示了 16 个字段中的 15 个。查看全部字段

{
  "found": true,
  "data": {
    "url": "https://www.linkedin.com/pulse/why-most-forecasting-models-fail-quarter-two-daniela-ruiz",
    "title": "Why most forecasting models fail in the second quarter",
    "body": "Suppose your forecast is built on last January's demand curve. By April, the assumptions underneath it have already moved twice.\n\nMost finance teams do not notice until the variance report lands, and by then the quarter is half over. The fix is not a better model. It is a shorter feedback loop between the actuals and the assumptions that produced the forecast.\n\nOver the last year we worked with a dozen mid-market finance teams rebuilding this loop. Three changes showed up in every team that closed its variance gap: weekly actuals instead of monthly, a single owner per assumption, and a standing fifteen minute review that only asks what changed.\n\nNone of this requires new tooling. It requires treating the forecast as a living document instead of a quarterly artifact.",
    "description": "Three changes that closed the variance gap for a dozen finance teams, and none of them required new software.",
    "author": "Daniela Ruiz",
    "authorUrl": "https://www.linkedin.com/in/daniela-ruiz-fpa",
    "authorFollowers": 18400,
    "createdUtc": 1755878400,
    "updatedUtc": 1755964800,
    "reactions": 612,
    "comments": 47,
    "image": "https://media.licdn.com/dms/image/D4E12AQF-forecast-cover/article-cover-image.jpg",
    "type": "article"
  }
}

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

参考

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

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

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

请求体

JSON,POST 到这个接口。

  • urlstring

    https://www.linkedin.com/pulse/why-most-forecasting-models-fail-quarter-two-daniela-ruiz

    公开的 LinkedIn 文章或新闻通讯期刊 URL,例如 https://www.linkedin.com/pulse/your-article-slug。配合 linkedin.search_posts_full 返回的 attachmentUrl,可以读取帖子背后的文章。

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

响应

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

datadata
  • authorstring

    Daniela Ruiz

    Display name of the person or organization that published the article. Populated whenever the provider has data for the entity.

  • authorFollowersinteger

    18400

    Follower count of the author at capture time.

  • authorUrlstring

    https://www.linkedin.com/in/daniela-ruiz-fpa

    Canonical LinkedIn profile or company URL of the author.

  • bodystring

    Suppose your forecast is built on last January's demand curve. By April, the assumptions underneath it have already moved twice. Most finance teams do not notice until the variance report lands, and by then the quarter is half over. The fix is not a better model. It is a shorter feedback loop between the actuals and the assumptions that produced the forecast. Over the last year we worked with a dozen mid-market finance teams rebuilding this loop. Three changes showed up in every team that closed its variance gap: weekly actuals instead of monthly, a single owner per assumption, and a standing fifteen minute review that only asks what changed. None of this requires new tooling. It requires treating the forecast as a living document instead of a quarterly artifact.

    Full body text of the article as plain text. Populated whenever the provider has data for the entity.

  • commentsinteger

    47

    Total comments on the article.

  • createdUtcnumber

    1755878400

    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.

  • descriptionstring

    Three changes that closed the variance gap for a dozen finance teams, and none of them required new software.

    Short summary of the article, as LinkedIn presents it in previews.

  • imagestring

    https://media.licdn.com/dms/image/D4E12AQF-forecast-cover/article-cover-image.jpg

    Cover image URL of the article.

  • reactionsinteger

    612

    Total reactions on the article.

  • titlestring

    Why most forecasting models fail in the second quarter

    Title of the article. Populated whenever the provider has data for the entity.

  • typestring

    article

    Kind of LinkedIn publication, e.g. article or issue (a newsletter edition).

  • updatedUtcnumber

    1755964800

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.

  • urlstring

    https://www.linkedin.com/pulse/why-most-forecasting-models-fail-quarter-two-daniela-ruiz

    Canonical URL of the article. Populated whenever the provider has data for the entity.

top level
  • foundboolean

    true

    False when the URL does not resolve to a readable LinkedIn article.

  • 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.article,就以统一格式的 JSON 返回 LinkedIn 数据。按 URL 读取公开的 LinkedIn 文章或新闻通讯期刊,包括完整正文、作者、发布时间和互动数据。无论哪个数据源提供服务,AnyAPI 都返回同一套统一的 schema。费用:每千次请求 US$5.65 起,以美元计价,无需订阅,也没有每月最低消费。过去 30 天,通过 AnyAPI 发起的 LinkedIn 文章 API 调用中有 93.0% 成功,响应时间中位数为 4.5 秒,共测量 215 次调用。

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

按 URL 读取公开的 LinkedIn 文章或新闻通讯期刊,包括完整正文、作者、发布时间和互动数据。响应是统一格式的 JSON,外层结构与每个 AnyAPI 接口相同,所以解析另一个接口只需换一个 URL,别的都不用改。

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

可以。新的 AnyAPI 账户自带 US$0.10 免费余额,无需绑卡,足够调用 17 次 LinkedIn 文章,每次 US$0.00565。

向 https://api.getanyapi.com/v1/run/linkedin.article 发送 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 调用这个接口。