Documentation Index
Fetch the complete documentation index at: https://docs.nordicfinancialnews.com/llms.txt
Use this file to discover all available pages before exploring further.
The Nordic Financial News API supports a polling pattern for keeping a local data mirror in sync. Use the updated_after parameter on the /articles and /stories endpoints to fetch only records that changed since your last sync.
How to poll for updates
Store your last sync timestamp
Start with an initial timestamp (e.g. when you first synced) and update the stored timestamp after each successful poll.
Request updated records
Pass updated_after with your stored timestamp:curl -H "Authorization: Bearer $API_KEY" \
"https://nordicfinancialnews.com/api/v1/articles?updated_after=2024-01-01T00:00:00Z&fields=id,title,published_at,content_type"
Process and repeat
Process the returned articles or stories, update your sync timestamp to the current time, then wait before polling again.
Polling example with articles and stories
LAST_SYNC="2024-01-01T00:00:00Z"
# Fetch new/updated articles since last sync
curl -H "Authorization: Bearer $API_KEY" \
"https://nordicfinancialnews.com/api/v1/articles?updated_after=$LAST_SYNC&fields=id,title,published_at,content_type"
# Fetch new/updated stories since last sync
curl -H "Authorization: Bearer $API_KEY" \
"https://nordicfinancialnews.com/api/v1/stories?updated_after=$LAST_SYNC"
How the updated_after parameter works
When updated_after is set:
- All matching records are returned in a single response (cursor pagination is disabled)
- ETag caching is disabled since the results are time-sensitive
- The response includes both newly created and recently modified records
Use the fields parameter to request only the fields you need, reducing bandwidth and response time. A 30-60 second polling interval works well for most use cases.
