Overview
  • More than 1500 APIs across payments, retail and corporate banking domains
  • Includes differentiated functionality such as multi product originations, bulk payments, and trade finance
  • Context sensitive adaptive APIs with intelligent pre and post-processing capabilities
  • Pre-integrated with Oracle solutions for core banking, payments, identity, security and API monetization
  • Robust consent, access, entitlement, limits management and approval framework
  • Ease to integrate into the banks information technology landscape
API catalogue

APIs are grouped into different categories based on business functions and its associated use cases. You can check out the products, API signatures, parameters, and response structure to understand the APIs from a functional perspective.

Trying out the APIs

APIs can be tried with a specific user context through proper authentication medium (OAuth 2.0) so that you can get an understanding of the request and response structure and can be integrated after complete understanding of the APIs.

There are specific set of APIs which are not contextual to user like fetching enumerations, products etc. and can be tried without any authentication.

To try the APIs, click on the particular API in the menu. You will see a ‘Try it out’ option against the respective API.

Please follow the steps mentioned below to try out:

1. Click on the Authorize button or the lock icon against the respective API.

2. Specify user credentials along with Client ID and Client Secret and click ‘Authorize’ to get the access token.

Available authorizations

3. Once you are logged in, the following screen is displayed.

Available authorizations

4. Click on Close button and invoke an API. e.g. /accounts.

Accounts REST API's for various account operations

5. Expand & click “Try it out” Execute. JSON response is shown below:

JSON Response

Curl


Request URL

http://mum00chx:3333/digx/v1/accounts

Server Response

CodeDetails
400Error: Bad Request
Response body
Download
{
	  "result": "SUCCESSFUL",
	  "contextID": "005Ta26auCMFw00Fzzx0g00005Cb000hmn,0:1",
	  "message": {
		"code": "DIGX_FW_NON_002",
		"type": "ERROR"
	  }
	}

Response headers
 cache-control: max-age=0, no-cache, no-store, must-revalidate  connection: close  content-encoding: gzip  content-type: application/json  date: Fri, 21 Sep 2018 12:10:30 GMT  expires: Wed, 11 Jan 1984 05:00:00 GMT  pragma: no-cache  server: Oracle-HTTP-Server  transfer-encoding: chunked  vary: Accept-Encoding  x-content-type-options: nosniff  x-frame-options: DENY  x-oracle-dms-ecid: 005Ta26auCMFw00Fzzx0g00005Cb000hmn  x-oracle-dms-rid: 0:1 

6. Note the Curl command. This token and other headers can be used to invoke other APIs.

Curl