API Documentation - Nordic Financial News

What You Can Access

Articles

Translated Nordic news articles

GET /api/v1/articles

Stories

Clustered related articles

GET /api/v1/stories

Companies

Nordic company profiles

GET /api/v1/companies

Countries

Nordic country data

GET /api/v1/countries

Exchanges

Stock exchange listings

GET /api/v1/exchanges

Search

Full-text search across content

GET /api/v1/search

Getting Started

1

Create an account and generate an API key

Sign up for a Nordic Financial News account, then navigate to Settings → API Keys to generate your key. API access is available on Plus and Pro plans.

2

Make your first request

curl -H "Authorization: Bearer YOUR_API_KEY" \
              https://nordicfinancialnews.com/api/v1/articles?limit=5

import requests resp = requests.get(
              "https://nordicfinancialnews.com/api/v1/articles",
              headers={"Authorization": "Bearer YOUR_API_KEY"},
              params={"limit": 5}, ) data = resp.json()
              print(data["data"][0]["title"])

require "net/http" require "json" uri =
              URI("https://nordicfinancialnews.com/api/v1/articles?limit=5")
              req = Net::HTTP::Get.new(uri) req["Authorization"] = "Bearer
              YOUR_API_KEY" res = Net::HTTP.start(uri.hostname, uri.port,
              use_ssl: true) { |http| http.request(req) } data =
              JSON.parse(res.body) puts data["data"].first["title"]

3

Explore the response

Every list endpoint returns a data array along with pagination cursors. Check the Documentation for complete response schemas and all available parameters.

Authentication

Authenticate every request with a Bearer token in the Authorization header.

Authorization: Bearer YOUR_API_KEY

Usage headers

Responses include headers to help you track your monthly usage:

Header	Description
X-Monthly-Limit	Your plan's monthly request allowance
X-Monthly-Remaining	Requests remaining this billing period
X-Monthly-Reset	ISO 8601 timestamp when your limit resets
X-Request-Id	Unique ID for request tracing and support

Key Concepts

Cursor Pagination

List endpoints use cursor-based pagination. The response includes a next_cursor value — pass it as the cursor query parameter to fetch the next page.

# First page GET /api/v1/articles?limit=25 # Next page GET
            /api/v1/articles?limit=25&cursor=eyJpZCI6...

ETags & Caching

Individual resource endpoints (e.g. GET /api/v1/articles/:id) return an ETag header. Send it back as If-None-Match on subsequent requests to receive a 304 Not Modified when the resource hasn't changed, saving bandwidth and not counting against your monthly limit.

Incremental Sync

Use the updated_after parameter (ISO 8601) on list endpoints to fetch only records that changed since your last sync. This is ideal for keeping a local mirror up to date.

Error Format

Errors follow the RFC 9457 Problem Details format:

{ "type":
            "https://docs.nordicfinancialnews.com/problems/not-found", "title":
            "Resource not found", "status": 404, "detail": "No article found
            with id 'abc123'." }

Next steps

Now that you understand the basics, you can explore the complete API Reference to learn about all available endpoints and parameters.

API Reference →

Nordic Financial News API