Skip to main content
The API uses RFC 9457 Problem Details for error responses.

​
Error format

{
  "type": "https://docs.nordicfinancialnews.com/problems/not-found",
  "title": "Resource not found",
  "status": 404,
  "detail": "No article found with id 'abc123'."
}
FieldDescription
typeURI identifying the error type
titleShort human-readable summary
statusHTTP status code
detailSpecific explanation for this occurrence

​
Status codes

CodeMeaningCommon cause
400Bad requestInvalid parameters or malformed request
401UnauthorizedMissing or invalid API key
403ForbiddenAPI key lacks required scope
404Not foundResource does not exist
429Too many requestsRate limit or monthly limit exceeded
500Internal server errorUnexpected server error

​
Rate limit errors

When you hit a rate limit, the response includes a Retry-After header indicating how many seconds to wait: 
HTTP/1.1 429 Too Many Requests
Retry-After: 60
Check the X-RateLimit-Remaining and X-Monthly-Remaining headers to monitor your usage proactively. See authentication for details on rate limits and monthly quotas.

​
Request tracing

Every response includes an X-Request-Id header. Include this ID when contacting support about a specific request.