SingleView Open Banking APIs work on robust authentication as a fundamental aspect to ensure secure and authorized access to API services and data. In this section, we'll guide you through the various authentication methods and best practices required to interact with our APIs securely.

To make a call to access SingleView Open Banking API services, the user must have the following required information to be mentioned in the header of requests:

• clientId
• clientCode
• signature
• Access Token

API Keys

clientId

clientId is an authentication value allotted to every registered user and is unique for every application added in the Console.

To know your clientId, go to Console > App settings > Credentials > Client ID.

clientCode

clientCode, displayed as Client Secret, is a highly-sensitive authentication value unique for every client app. The value can be modified when required.

To know your clientCode, go to Console > App settings > Credentials > Client Code.

signature

signature is an encrypted string that acts as a crucial part of the authentication process. It ensures and confirms the information included in the request is genuine and hasn't been modified.

Access Token

Access Token is a security parameter that enables the users to sent authorized requests to the SingleView APIs. It is obtained during the initial login process. It is mandatory for a user to include a valid access token to facilitate their requests to access SingleView API services.