Fetching the transactions

Requirements

Fetch the transactions from the account selected in the Verify and Pay flow to do the payment. Regardless of whether the verification succeeded or failed, the transactions will be available via the ID provided in the response to the flow's original request. This identifier can also be retrieved from the flow_id query parameter in the callback URL.

GET https://api.finx-s.qwist.cloud/artifacts/{id}?artifact_type=transactions

Authorization: Basic {Base64(clientId:clientSecret)}

Response

{
    "id": "67003b72-bb21-44a9-8846-55944fa6ed6f",
    "created_at": "2026-07-03T13:11:35.672295+00:00",
    "type": "transactions",
    "raw_result": [
        {
            "account_id": "A1154933568075214731.1",
            "account_number": "1280235001",
            "amount": -55.99,
            "booked": true,
            "booked_at": "2025-07-03T00:00:00+00:00",
            "categories": [
                {
                    "id": 101,
                    "parent_id": null,
                    "name": "Mobility"
                }
            ],
            "created_at": "2026-07-03T13:11:20.609757+00:00",
            "modified_at": "2026-07-03T13:11:31.878084+00:00",
            "settled_at": "2025-07-03T00:00:00+00:00",
            "transaction_code": 999,
            "transaction_id": "T1154933568075214731.1",
            "contract_id": "C1154933568075214731.1",
            "type": "Unknown",
            "external_id": "7c5bba49-f07a-4b5e-a956-c28af1a61213",
            "bank_code": "20050550",
            "mandate_reference": "VMH010127450001",
            "purpose": "HVV",
            "bic": "HASPDEHHXXX",
            "creditor_id": "DE3900100000393766",
            "end_to_end_reference": "0011243786 4072661078",
            "currency": "EUR",
            "sepa_remittance_info": "HVV Hamburger Hochbahn AG",
            "iban": "DE45200505501280235001",
            "name": "Hamburger Hochbahn AG"
        },
			{
            "account_id": "A1154933568075214731.1",
            "account_number": "582461009",
            "amount": -79.84,
            "booked": true,
            "booked_at": "2025-07-05T00:00:00+00:00",
            "categories": [
                {
                    "id": 203,
                    "parent_id": null,
                    "name": "Food"
                },
                {
                    "id": 94,
                    "parent_id": 203,
                    "name": "Groceries"
                }
            ],
            "created_at": "2026-07-03T13:11:20.621085+00:00",
            "modified_at": "2026-07-03T13:11:30.556226+00:00",
            "settled_at": "2025-07-05T00:00:00+00:00",
            "transaction_code": 999,
            "transaction_id": "T1154933568075214731.3",
            "type": "Unknown",
            "external_id": "16c3e2ee-93de-4ebc-bf7c-915bf4ad85d3",
            "bank_code": "50040000",
            "purpose": "ABWA+BIO COMPANY GmbH//Hamburg/DE",
            "bic": "COBADEFFXXX",
            "end_to_end_reference": "482092488274022",
            "currency": "EUR",
            "sepa_remittance_info": "2023-02 Debitk.00 VISA Debit+ABWA+BIO COMPANY GmbH//Hamburg/DE",
            "iban": "DE37500400000582461009",
            "name": "BIO COMPANY GmbH"
        }
    ],
    "meta": {
        "user_id": 1154933568075214731
    }
}

Response schema

Section	Description
`id`	Unique identifier of the flow and the report
`created_at`	Creation time
`type`	The type of the artifact to retrieve. It must be `artifact_type`
`meta`	Possible metadata entries. It usually includes the user id
`raw_result`	The full generated report in JSON format. This raw_result schema entirely depends on the `artifact_type` sent in the request. The schemas can be filtered by `type` in the API Reference section.

Error handling

The nrich API uses standard HTTP status codes and returns a structured error object in the response body.

Error response structure

{
  "error": {
    "code": 1000,
    "group": "client",
    "description": "Request body doesn't match input schema.",
    "data": {
      "redirect_uri": ["Not a valid URL."]
    }
  }
}

Field	Description
`code`	nrich-specific numeric error code.
`group`	Error category: `client`, `user`, `bank`, `general`, or `connectivity`.
`description`	Short human-readable summary.
`data`	Field-level validation details (on `400` errors).

HTTP status codes

Code	Meaning	What to do
`200 OK`	Success.	Parse the response body.
`400 Bad Request`	Invalid or missing parameters.	Check `error.data` for the specific field.
`401 Unauthorized`	Token missing or expired.	Refresh using your `refresh_token` and retry.
`403 Forbidden`	Valid token, insufficient scope.	Verify your credentials have the required scopes.
`404 Not Found`	Resource not found or not yet created.	Confirm the ID is correct; some resources only exist after the user completes the flow.
`423 Resource Locked`	Resource temporarily locked during migration.	Retry with exponential backoff (seconds → minutes).
`500 Internal Server Error`	Unexpected server error.	Retry with backoff; contact support if it persists.

🚧
Implement 423 retry logic
423 can occur after system updates. Your application must handle it with incremental backoff - do not surface it directly to users.

Common nrich error codes

Code	Group	Description
`1000`	client	Invalid request - check `data` for field details
`1002`	client	Entity not found
`1008`	client	Resource busy - implement retry with backoff
`10000`	user	Login credentials are invalid
`10001`	user	PIN is invalid
`10004`	user	TAN is invalid
`10007`	user	PIN change required at the bank
`20000`	bank	Processing at the bank not possible
`20003`	bank	Bank under maintenance
`30000`	general	Processing at nrich not possible
`30005`	general	Task has expired
`40000`	connectivity	Bank not supported