Use the updated_after parameter on the /articles and /stories endpoints to fetch only records that changed since your last sync.
Polling pattern
Store your last sync timestamp
Start with an initial timestamp (e.g. when you first synced) and update it 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_en,summary_en,published_at"
Process and repeat
Process the results, update your timestamp to the current time, then wait before polling again.
Example
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_en,summary_en,published_at"
# Fetch new/updated stories since last sync
curl -H "Authorization: Bearer $API_KEY" \
"https://nordicfinancialnews.com/api/v1/stories?updated_after=$LAST_SYNC"
How updated_after works
When updated_after is set:
- All matching results are returned in a single response (cursor pagination is disabled)
- Caching is disabled since the results are time-sensitive
- Results include both newly created and updated 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.
