Open BankingB2B SuiteERP Integration
GuidesAPI ReferenceChangelog
Menu

Categories

Open BankingB2B SuiteERP Integration

  • GENERAL INFORMATION

    • Documentation guide
    • SingleView B2B Core APIs
    • Platform architecture
  • GETTING STARTED

    • Integration guide
    • Become a user
    • Prerequisites for Sandbox
    • Establishing secure connection
    • Authenticating your request
    • Making your first test api call
    • Prerequisites for production
    • Moving to production
  • AUTHENTICATION

    • Header parameters
    • Obtain access token
    • Generate signature
  • Data APIs

    • Account statement
    • Balance enquiry
    • IBAN verification
    • POS transactions
    • Raw statement
  • Payment APIs

  • SADAD

  • RESOURCES

    • POR Details
    • Error codes
  • API Archives


Obtain access token

Generate an access token to authenticate your API requests

Before calling any protected API, your application must obtain an access token from the SingleView authentication service. The access token identifies your application and authorizes it to access the APIs included in your subscription.

Access tokens are generated using the Client Credentials grant type and must be included in the Authorization header of every subsequent API request.

Obtain access token

Endpoint

Method

Headers

/v1/api/svplatform/tokenOauth2

POST

  • CompanyId
  • SVReferenceId
  • DateTimeStamp
  • Device

Sample request

Sample request to obtain access token
curl --location 'https://sandboxapi.onesingleview.com/v1/api/svplatform/tokenOauth2' \
--header 'CompanyId: MYCOMPANY' \
--header 'SVReferenceID: BEMC0001' \
--header 'DateTimeStamp: 2025-01-02T10:20:39' \
--header 'Device: Web' \
--header 'Content-Type: application/json' \
--data-raw '{
"clientId": "abcdef83643f61c975",
"clientCode": "zyxvw95cE163C03b7d1",
"grant_type": "client_credentials"
}'

Request parameters

Parameter

Type

Description

Required

clientId

String

Client identifier issued during onboarding.

Yes

clientCode

String

Client secret or client code issued during onboarding.

Yes

grant_type

String

OAuth grant type. Set to client_credentials.

Yes

Sample Response

Sample response of a successfully obtained access token
{
"access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkYXRhIjoiTDNyMmpxV29JS2I4MTNodDBNMlZ4WGpFZmR6WFNWaTFad3B5QnlkOVpHelZXR2ZwUmFQNUV1TXl6S1Aybi94Y0lwR2V5STNNMkdPL1pqakd4ZG0yclJKUkdhRXlaWGNpWnZnOHArMWIyOGtOQTVkZ0VKajVVSEdiTmtNPSIsImlhdCI6MTczNTgwMTQ3NywiZXhwIjoxNzM1ODA1MDc3fQ.Bh7LFkvxNFrLe9dmH5rURWjGpES-u4z2EGeyrNM7z6E",
"token_type": "Bearer",
"expires_in": "6000"
}

Response parameters

Parameter

Description

access_token

The OAuth access token used to authenticate subsequent API requests.

token_type

Indicates the authentication scheme. The value is Bearer.

expires_in

The validity period of the access token, in seconds.

Using the Access Token

After obtaining the access token, include it in the Authorization header of every protected API request.

Header field for access token
Authorization: Bearer <access_token>

Replace <access_token> with the token returned by the authentication service.

Best Practices

  • Request a new access token only when the current token has expired
  • Store access tokens securely and avoid exposing them in logs or client-side applications
  • Protect your clientId and clientCode as confidential credentials
  • Always send authentication requests over HTTPS
  • Use the access token in conjunction with the required digital request signature for all protected API calls
Updated June 25, 2026

PreviousHeader parametersNextGenerate signature
Was this helpful?