Open BankingB2B SuiteERP Integration
GuidesAPI ReferenceChangelog
Menu

Categories

Open BankingB2B SuiteERP Integration

  • GENERAL INFORMATION

    • Documentation guide
    • SingleView Open Banking
    • KSAOB standards
    • Security best practices
  • GETTING STARTED

    • Integration guide
    • Developer console
    • Establish secure connection
    • Generate access token
    • Make test raw data API call
    • Make test data use case API call
  • CONSENT MANAGEMENT

    • Overview
    • Create a consent
    • Retrieve consent details
    • Revoke a consent
  • Raw Data APIs

    • Introduction
    • View accounts
    • View balance
    • View transactions
    • Identify account holders (Parties)
    • Review direct debits
    • Review scheduled payments
    • Review standing orders
  • DATA USE CASE APIS

  • Plug-and-Play Integrations

    • Payly
  • RESOURCES

    • Errors & codes
    • Collections
    • API version management
    • Bank connectivity
  • API Archives


Make test raw data API call

Learn how to retrieve customer-permissioned banking data by creating a consent and accessing SingleView Raw Data APIs

Raw Data APIs provide direct access to banking information shared by customers through the Open Banking framework. Before accessing any data, you must obtain the customer's consent and ensure the consent is active.

Prerequisites to make a test call

Before making a Raw Data API request, ensure that you have:

  • Created a Console account
  • Configured your application
  • Established a secure connection
  • Generated the required authentication credentials

Example Data Retrieval Flow

The following workflow illustrates a typical Raw Data API journey:

Create Consent
↓
Customer Authorizes Consent
↓
Retrieve Consent Details
↓
Select Raw Data Service
↓
Make API Request
↓
Receive Banking Data

Step 1: Create and Authorize a Consent

Open Banking data can only be accessed after obtaining explicit customer consent.

To create a consent:

  1. Submit a Create Consent request
  2. Define the permissions required by your application
  3. Specify the consent validity period
  4. Redirect the customer to complete authorization
  5. Verify that the consent status is Authorized
Outcome

An active consent that authorizes access to customer banking data.

Step 2: Retrieve Consent Details

Before making a data request, confirm that the consent is valid and active.

Use the Retrieve Consent Details endpoint to:

  • Verify consent status
  • Confirm granted permissions
  • Validate consent expiration
Outcome

Confirmation that the requested data can be accessed.

Step 3: Make a Raw Data API Request

Once consent has been successfully authorized, you may access the available Raw Data APIs.

The following services are available:

  • View accounts
  • View balance
  • View transactions
  • Identify account holders (Parties)
  • Review direct debits
  • Review scheduled payments
  • Review standing orders

Expected Response

A successful request returns customer-permissioned banking data in a standardized format, subject to:

  • The permissions granted by the customer
  • The data made available by the financial institution
  • The consent validity period

If a consent is revoked, expired, or does not include the required permission scope, the request will be rejected.

Updated July 2, 2026

PreviousGenerate access tokenNextMake test data use case API call
Was this helpful?