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


Making your first test api call

Validate your integration by testing the APIs available in your subscription

After establishing a secure connection and successfully authenticating your requests, you are ready to make your first API call in the sandbox environment.

The SingleView B2B API Suite allows you to test the APIs that are enabled as part of your subscription. Testing your integration helps verify connectivity, authentication, request formatting, and response handling before moving to the production environment.

Before you begin

Ensure that you have completed the following:

  • Registered and onboarded your organization
  • Received sandbox access and API credentials
  • Established a secure mTLS connection
  • Generated a valid access token
  • Configured request signing
  • Reviewed the API Reference for the service you intend to test

Select an API to test

Choose any API that is included in your subscription and submit a request using the sandbox environment.

Data APIs

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

Payment APIs

  • Payouts
    • Single payment
    • Bulk payment
  • Payroll payouts
  • SADAD Bills
  • SADAD MOI

Testing workflow

The typical workflow for testing an API is as follows:

  1. Select an API from your subscribed services
  2. Review the endpoint requirements in the API Reference
  3. Construct the request with the required headers, authentication token, and digital signature
  4. Submit the request to the sandbox endpoint
  5. Review the response and verify the returned data or transaction status
  6. Handle any validation or error responses as documented

Validate your results

When testing your integration, verify that:

  • Authentication is successful
  • Request signatures are accepted
  • Required headers are correctly populated
  • Request payloads are valid
  • Responses match the documented schema
  • Error scenarios are handled appropriately by your application

Completing these validations helps ensure your application is ready for production deployment.

What's next?

Once you have successfully tested the APIs included in your subscription and verified your application's behavior, you can proceed with the production readiness activities.

Refer to Moving to Production for the final steps required to deploy your integration and begin processing live business transactions.

Updated July 10, 2026

PreviousAuthenticating your requestNextPrerequisites for production
Was this helpful?