Wednesday, October 28, 2026
Track Breaking-News Updates with revisedDate
Track Breaking-News Updates with revisedDate
News isn't static. A story breaks, then the publisher corrects a number, adds a quote, or updates the
headline as the situation develops. If you only track publish time, you'll miss those revisions.
finlight exposes a revisedDate so you can catch stories that changed after they were first published.
Order by latest revision
To surface recently updated articles, sort by revisedDate on POST /v2/articles:
curl -X POST https://api.finlight.me/v2/articles \
-H "X-API-KEY: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"tickers": ["AAPL"],
"orderBy": "revisedDate",
"order": "DESC",
"pageSize": 20
}'
When you order by revisedDate, each article includes both its original publishDate and its
revisedDate:
{
"title": "Apple expands services guidance after earnings call",
"publishDate": "2026-06-18T09:00:00.000Z",
"revisedDate": "2026-06-18T14:30:00.000Z"
}
Detecting what actually changed
Comparing the two timestamps tells you which stories were updated and how long after publication:
- If
revisedDateis later thanpublishDate, the story was revised. - The gap between them tells you how fresh the update is, which is useful for flagging fast-moving stories.
A simple polling loop that orders by revisedDate and remembers the last revisedDate it saw will
pick up every revision since the previous run, without re-processing unchanged articles.
Good to know
revisedDatereflects when the news provider last revised the article, not when finlight ingested it. UsecreatedAtif you want finlight's ingestion time instead.- The field is returned when you order by
revisedDate. Pair it with any filters you like (tickers,categories,query). - Every official finlight SDK accepts
revisedDateas the order field too, so you don't need raw HTTP for this. In TypeScript that'sorderBy: 'revisedDate'; in Python,orderBy="revisedDate".
