Skip to main content
Problem type: https://docs.nordicfinancialnews.com/problems/invalid-parameter
The API returns this problem type with HTTP 400 when one of your query parameters cannot be used. It is the most specific of the error types: the response names the parameter at fault in its own parameter member, and detail explains what was wrong with it.

​
Example response

parameter is an extension member on top of the standard RFC 9457 fields. Read it rather than parsing detail: it is a bare parameter name, stable enough to switch on, whereas detail is prose that can be reworded.

​
What triggers it

Four shapes of mistake, all reported the same way:
  • An unrecognized value for a fixed-list filter. content_type, sector, market_segment, status, event_type, sentiment and sort all validate against a known set, and detail lists the accepted values. Company filters such as ticker behave the same way, naming every value that failed to resolve.
  • Two parameters that cannot be combined. cursor with q, mode=semantic with cursor, sort or updated_after, ids with cursor. detail says which pairing was rejected and why.
  • A parameter missing its companion. mode=semantic and sort=relevance both need q, since neither ranking is defined without a query.
  • A cursor that is invalid or expired. Cursors are opaque and time-limited. Restart the walk from the first page rather than editing one by hand.
Not every unusable value produces this error. Some filters ignore what they do not recognize and return an empty page instead, which is a different failure to debug. Error handling sets out which filters validate strictly and which drop silently.

​
The fields variant

An unrecognized name in the fields parameter returns this same problem type, but in a different shape:
The offending names arrive in an unknown_fields array, which makes them easy to log. In exchange, this variant carries no parameter member and a different title. Code that reads parameter unconditionally will find it missing, so check for it before you use it. The allowed names are per resource: a field that exists on an article does not exist on a company. Field projection lists the set for each. An empty fields= returns the ordinary variant instead, with parameter set to fields.

​
How to fix it

Fix the request. There is nothing to retry, and repeating an identical call returns an identical error while still counting against your rate limit and monthly quota. Read parameter to find the offending value in your request builder, then detail for the accepted values. If the parameter looks correct, check it is spelled as the API expects and that you are sending it to an endpoint that accepts it: a parameter that is valid on one resource is not automatically valid on another, and a company-scoped path rejects filters the flat equivalent accepts.
Last modified on October 23, 2026