Skip to main content
Problem type: https://docs.nordicfinancialnews.com/problems/not-found
The API returns this problem type with HTTP 404 when the thing you asked for cannot be resolved. Three things produce it:
  • The path is under /api/v1 but matches no route, usually a typo in the resource name.
  • The path is valid but the identifier in it matches no record.
  • The endpoint exists but is not enabled for your API key, in which case it is hidden rather than refused.

​
Example response

detail is a fixed string. It does not echo the identifier you sent and it does not say which of the three causes applies, so log the request URL yourself if you want to know what failed. The instance value is the request ID, which is what support needs to look one up.

​
How to fix it

Retrying is pointless. A 404 reflects the state of your request, not a transient condition. Check the path first, then the identifier. Only paths under /api/v1 reach this problem type. A request outside that prefix, such as a wrong version number, gets a generic HTML 404 from the site rather than a JSON problem body, so an unparseable 404 usually means the prefix is wrong. A list endpoint is the fastest way to confirm an identifier exists and is spelled as the API expects, and identifier formats vary by resource: several accept a human-readable value as well as an ID. The API reference gives the accepted form per endpoint. If both look right, treat entitlement as the next suspect. Because an endpoint your key cannot reach returns 404 rather than 403, a 404 is not proof the resource does not exist. Contact support with the instance value if you believe you should have access.
Last modified on September 8, 2026