Instant Reporting API: FAQ – Nordea Open Banking Support

Reference:

Why do we get zero transactions when calling:

GET /corporate/premium/v4/accounts/{account_id}/transactions

while requesting the same endpoint (and the same account) with from_date and to_date parameters:

GET /corporate/premium/v4/accounts/{account_id}/transactions?from_date=yyyy-mm-dd&to_date=yyyy-mm-dd

works as expected?

If from_date (to_date) parameter is not provided, then only last two days of transactions are returned by default (if any exist). It can be checked using Account details endpoint:

GET /corporate/premium/v4/accounts/{account_id}

and identifying latest_transaction_booking_date field.

How to properly use from_transaction parameter while calling:

GET /corporate/premium/v4/accounts/{account_id}/transactions

to get only transactions that are booked after specified transaction ID? Can we use from_transaction parameter without including from_date parameter?

The latest transaction in the response list is on top. To use from_transaction parameter you need to use transactions that are in range of transaction value_date:

GET /corporate/premium/v4/accounts/{account_id}/transactions?from_date=yyyy-mm-dd&from_transaction={transaction_id}

Then in the response you will get only transactions starting with from_transaction parameter.

From_date and to_date parameters are on the highest priority by default . If from_date is not explicitly provided then it's set to yesterday's date. The only way to use from_transaction parameter solely and get a valid response is when some transactions have been booked since yesterday. In other cases you need to use from_transaction with providing date for from_date parameter.

In your documentation:

How to start traffic with Instant Reporting API

it's stated that I need to know:

Your company's Corporate Netbank administrator's logon ID. Check with your company's Corporate Netbank administrator, if your company has one or several administrators.

I do not understand where the Corporate Nethanks administrator´s Logon ID should be supplied in the authentication process.

Please refer to: Corporate Access Authorization: FAQ

We want to use Premium Instant Reporting API and we encounter authorizer_id parameter - how will it affect our data flow? Does it mean that every time we make an API call, an administrator has to accept? Is it mandatory to do this every time a call is made?

Please refer to: Corporate Access Authorization: FAQ

While requesting Instant Reporting API endpoint:

GET /corporate/premium/v4/accounts/{account_id}/transactions

we encounter the following error ("code": "error.resource.denied", "description": "Token does not authorize the requested action."):

{
"code": "error.resource.denied",
"description": "Token does not authorize the requested action."
}
],
"request": {
"url": "/premium/v4/accounts/DK12345678901234-DKK/transactions"
}
},
"group_header": {
"creation_date_time": "2025-01-13T14:51:14.906244662Z",
"http_code": 403,
"message_identification": "34f349501527165e"
}

What could be the reason?

Please refer to: Corporate Access Authorization: FAQ

While requesting Instant Reporting API endpoint:

GET /corporate/premium/v4/accounts

we encounter the following error ("code":"error.signature.invalid","description":"Signature is invalid."):

Status: Unauthorized
Response: {"group_header":{"message_identification":"0f8cb89e9007166e","creation_date_time":"2024-12-12T11:35:43.246569632Z","http_code":401},"error":{"request":{"url":"/corporate/premium/v4/accounts"},"failures":[{"code":"error.signature.invalid","description":"Signature is invalid."}]}}

What might be the reason?

Please refer to: Corporate Access Authorization: FAQ

Do we need to do the authorization process through Nordea ID application every time we want to use GET /corporate/premium/v4/accounts (Instant Reporting API)?

Please refer to: Corporate Access Authorization: FAQ

We are testing the authorisation flow in production for Instant Reporting API and encountering an issue. Our observations when making requests are as follows:

POST /corporate/v2/authorize

returns success (access_id and client_token), whilst:

PUT /corporate/v2/authorize/<access_id>

results in a 408 timeout after approximately 680ms with the error response: {"code": "error.request.timeout", "description": "Authorization request timeout."}

What could be causing this timeout in production? Is the authorisation flow different between sandbox and production environments? We are using authorizer_id: "70311198" from sandbox testing.

Please refer to: Corporate Access Authorization: FAQ

Q:

Is there any time limit for completing all calls until all the requested transactions are fetched?

Yes, such time limit exists and it is 10 minutes. We strongly recommend to break the requests into shortest possible date ranges to avoid exceeding mentioned limit.

Why are we getting: "code": "error.request.timeout", "description": "Authorisation request timeout." error when executing the following authorisation flow for Instant Reporting API? The requests are milliseconds apart from each other, so should not result in a timeout. Logs:

Request

URL : POST https://open.nordea.com/corporate/v2/authorize

Headers:
Digest: SHA-256=sCwtlbfL/8RNRhH5ypIUaWAeu***7KrRnuz8B+UfKE18T0=
Signature: keyId="63bb***df53c",algorithm="rsa-sha256", headers="(request-target) x-nordea-originating-host x-nordea-originating-date content-type digest",signature="KrC3VyVkh***m2HYfT3PO03Ta/tow=="
X-IBM-Client-Id: 63bb***df53c
X-IBM-Client-Secret: ***
X-Nordea-Originating-Date: Tue, 23 Dec 2025 10:00:27 GMT
X-Nordea-Originating-Host: open.nordea.com
Accept: application/json

Body:
{
"agreement_number": "12***46",
"duration": 525600,
"scope": [
"ACCOUNTS_BROADBAND"
]
}

Response

Status Code: 201 Created

Body:
{
"group_header": {
"message_identification": "05c993a6347b1692",
"creation_date_time": "2025-12-23T10:00:28.924310199Z",
"http_code": 201
},
"response": {
"access_id": "0422ea1f-***-2ccec1339945",
"status": "CREATED",
"client_token": "eyJjdHkiOi***qql1bRfPYPerdv28RFCfjA",
"_links": [
{
"rel": "status",
"href": "/v2/authorize/0422ea1f-***-2ccec1339945"
}
]
}
}

Request

URL : PUT https://open.nordea.com/corporate/v2/authorize/0422ea1f-***-2ccec1339945

Headers:
Authorization: Bearer eyJjdHkiOiJKV1***31u6dg.qql1bRfPYPerdv28RFCfjA
Digest: SHA-256=MQE2D5kFl5HUnGlpKc69RVj/vtWcTQThmc1uo***AzcJf8=
Signature: keyId="63bb***f53c",algorithm="rsa-sha256", headers="(request-target) x-nordea-originating-host x-nordea-originating-date content-type digest",signature="Pr0OIxTja***i8nW0h1MBhMwKSuv55dnqw=="
X-IBM-Client-Id: 63b***df53c
X-IBM-Client-Secret: ***
X-Nordea-Originating-Date: Tue, 23 Dec 2025 10:00:28 GMT
X-Nordea-Originating-Host: open.nordea.com
Accept: application/json

Body:
{
"authorizer_id": "6***8-0***8"
}

Response

Status Code: 408 Request Timeout
Body:
{
"group_header": {
"message_identification": "05c993d7347b1692",
"creation_date_time": "2025-12-23T10:00:29.667141957Z",
"http_code": 408
},
"error": {
"request": {
"url": "/v2/authorize/0422ea1f-***-2ccec1339945"
},
"failures": [
{
"code": "error.request.timeout",
"description": "Authorization request timeout."

Please refer to: Corporate Access Authorization: FAQ

In Sweden, what factors can cause a transaction_id to change over time for the same transaction? An example below:

"group_header": {
"message_identification": "35b047492df21681",
"creation_date_time": "2026-02-02T08:01:01.700381021Z",
"http_code": 200
},
"response": {
"transactions": [
{
"currency": "DKK",
"narrative": "30***61",
"message": "30***61 null",
"status": "billed",
"amount": "32106.00",
"transaction_id": "H90***80",
"booking_date": "2026-02-02",
"value_date": "2026-02-02",
"type_description": "OVERFØRSEL",
"counterparty_name": "W***S",
"counterparty_address": "N***ej 9 7***d",
"transaction_date": "2026-02-02",
"balance_after_transaction": "6456659.17"

"group_header": {
"message_identification": "0dfef3ec347b1692",
"creation_date_time": "2026-02-06T09:16:53.575663776Z",
"http_code": 200
},
"response": {
"transactions": [

{
"currency": "DKK",
"narrative": "30***61",
"message": "30***61 null",
"status": "billed",
"amount": "32106.00",
"transaction_id": "P90***79",
"booking_date": "2026-02-02",
"value_date": "2026-02-02",
"type_description": "OVERFØRSEL",
"counterparty_name": "W***S",
"counterparty_address": "N***ej 9 7***d",
"transaction_date": "2026-02-02",
"balance_after_transaction": "-540017.75"

Transaction_ids beginning with "H" indicate unbooked transactions. This occurs for transactions that are preliminarily booked to accounts on the day the transaction is retrieved. Online bookings appear immediately, even though they are not finally processed until the following day. Once the transaction is finally booked, the transaction_id changes and begins with "P".

The same principle applies to the "balance_after_transaction" field, which is also updated following final booking.

Do transactions with identical booking_date and value_date values lack chronological sorting? When fetching same-day transactions (e.g., from_date=2026-03-27&to_date=2026-03-27), what sorting applies? Or do transactions maintain descending chronological order when booking_date and value_date match?

Initially, we sort transactions by booking_date in descending chronological order, from newest to oldest. For transactions sharing identical booking_date values, we apply descending chronological sorting by value_date. Finally, we sort by transaction_id to resolve any remaining ties.

We attempt to call the Authorize endpoints, but our Corporate Netbank administrators are not prompted to authenticate in the app.

POST /corporate/v3/authorize
PUT /corporate/v3/authorize/564a09f0-***-4a3f4081f828
GET /corporate/v3/authorize/564a09f0-***-4a3f4081f828

{'message_identification': '066bafc43780169b', 'creation_date_time': '2026-04-16T09:43:56.599056712Z', 'http_code': 200}, 'response': {'status': 'PENDING', '_links': [{'rel': 'status', 'href': '/v3/authorize/180d0dd1-***-0a44c93469ad'}]}}

What could be the reason?

The issue may be due to missing signing rights in Corporate Netbank, which your CN administrator should check.

Note: We cannot share the list of users with signing rights. Please ask your Corporate Netbank administrator for verification. For more help, see:

Nordea Corporate Netbank contacts

Related Questions

Reference: