Introduction

Raw Data APIs enable applications to securely access customer financial data from participating banks after obtaining explicit user consent.

These APIs allow developers to retrieve key financial information such as account details, balances, transaction history, and payment instructions. raw Data APIs form the foundation for building financial services such as personal finance tools, credit assessment platforms, and financial analytics applications.

All data access is consent-driven, secure, and compliant with Open Banking standards.

Accessing Raw Data API services

Access to Raw Data APIs is controlled through a secure, consent-driven process. Before any financial data can be retrieved, the customer must explicitly authorize the application to access their account information.

This process ensures that data sharing complies with Open Banking principles, where the customer remains in control of how their financial data is accessed and used.

Consent-Based Access

Raw Data APIs can only be accessed after obtaining customer consent. During the consent process, the application requests permission to access specific financial data from the user’s bank account.

The user is then redirected to their bank’s authentication interface, where they securely log in and approve the requested permissions. Once the consent is granted, the application receives a consent ID, which is used to retrieve the authorized financial data.

Authentication Requirements

To access Raw Data APIs, the application must first authenticate itself with the SingleView platform using OAuth2 client credentials. This generates an access token that is required for all subsequent API calls.

Each API request must include:

• A valid access token
• A valid consent ID
• Required request identifiers based on the service

Available APIs & Data Scopes