The Nordic Financial News API supports field projection on all list and detail endpoints. Use the fields query parameter to request only the fields you need. Selecting specific fields reduces payload size and optimizes database queries.
How to use field projection
Pass a comma-separated list of field names in the fields query parameter:
Available fields by resource
The following fields can be requested with the fields parameter for each Nordic Financial News API resource type.
Articles
id, title, article_url, content_type, published_at, updated_at, category, source, company_ids, country
Stories
id, title, summary, published_at, updated_at, article_count, article_ids, country, category, company_ids
Calendar events
id, title, description, event_type, status, date_precision, fiscal_period, scheduled_at, timezone, local_time, scheduled_at_changed_at, source_article_id, source, company_id, company, country, dividend, updated_at
Companies
id, name, slug, ticker, former_tickers
Countries
id, name, iso2_code
Exchanges
id, name, mic_code, acronym, country
Indices
id, name, symbol, pan_nordic, exchange
Categories
id, name
Sources
id, name, domain, country, source_type
Unrecognized field names
A name that is not in the list for the resource you are querying returns an error. The API does not quietly ignore it. You get a 400 carrying the invalid parameter problem type, with the names it did not recognize in an unknown_fields array.
The lists are per resource, so a name that works on one endpoint is not automatically valid on another. Passing fields= with nothing after it is also an error.
Field projection is especially useful with real-time updates to minimize bandwidth when polling frequently. Last modified on September 9, 2026