LinkedIn Article API
Read a public LinkedIn article or newsletter issue by URL, including its full body text, author, publication time, and engagement counts.
$6.16/1k req, pay per request, no subscription.
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.
Others also viewed
{"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 more fields}
Pricing
LinkedIn Article API pricing
Try it
Get LinkedIn article in one request
This sample shows 15 of 16 fields. See every field
{
"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"
}
}Full parameter and response reference - every field, type, and example for this endpoint.
Reference
One request, one response shape.
Every field you send and every field you get back, each with a real example.
Last verified 2026-11-22 · uptime and latency measured over 30d
Request body
JSON, posted to this endpoint.
- urlstring
https://www.linkedin.com/pulse/why-most-forecasting-models-fail-quarter-two-daniela-ruiz
Public LinkedIn article or newsletter issue URL, e.g. https://www.linkedin.com/pulse/your-article-slug. Pair it with the attachmentUrl returned by linkedin.search_posts_full to read the article behind a post.
Response
JSON, one example value per field.
- 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.
- 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.
FAQ
About the LinkedIn Article API
The AnyAPI LinkedIn Article API returns LinkedIn article data as normalized JSON from one POST call to /v1/run/linkedin.article. Read a public LinkedIn article or newsletter issue by URL, including its full body text, author, publication time, and engagement counts. AnyAPI returns one normalized schema whichever source serves it. It costs from $6.16 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 97.5% of LinkedIn article calls through AnyAPI succeeded, with a median response time of 4.0 seconds across 837 measured calls.