This document provides a technical overview of available endpoints, request parameters, and response schemas for the nrich API. While this reference offers essential structural information, it is not a comprehensive implementation guide.

📘
For detailed implementation guidance
Refer to the following product specific guides:

Financial Data

Multi Banking

Account Verification

Disposable Income Verification

Risk Insights

Payments

The implementation guides are essential for successfully integrating the nrich API, providing detailed instructions, best practices, and code examples.

Message formats

Request and response payloads are sent as JSON using UTF-8 encoding. Date properties are represented as ISO 8601 strings. For combined date and time representations (date-time), the time is in UTC and the format will always contain a timezone designator.

# Format specification
"YYYY-MM-DDThh:mm:ss.sss[sss]±hh:mm"

# Concrete examples
"2026-05-05T09:05:13.969065+00:00"
"2026-05-05T09:05:13.969+00:00"

HTTPS and TLS

The nrich API serves traffic over HTTPS, and will include an HSTS response header in order to let browsers and other client software enforce this. TLS v1.2 or higher is required.