1. Rest API Documentation
  2. Rest API Services - Overview

1 Rest API Services - Overview

Oracle Banking Treasury Management has adopted the industry standard of providing light-weight services through Representational State Transfer (popularly known as REST) services. These lightweight services support the current trend of mobile/tablet based applications. These services help to improve the response time for tablet/mobile applications, as these applications are very chatty, involves numerous hits to the server and the expected response time is minimal for each of the requests.

The REST/Fine grain services are listed below.
  • Derivatives
  • Exchange Traded Derivatives Portfolio Details
  • Foreign Exchange Details
  • Islamic Derivatives
  • Islamic Money Market Details
  • Money Market Details
  • OT Options
  • Securities Market Details
  • Securities Portfolio Details
  • Securities Repo Details
  • Settlement Instructions
More information on the above listed services can be found in the respective sections of the User manual.

Each of the services listed above are a URL. These URLs can be tested using any of the available browser plug-ins like Postman, RestEasy etc.. Also these services can be integrated with an API manager depending on its use. Below is the format to get contract example which takes the contract reference number as the input.

http://(IP):(Port)/ForeignCurrencyExchangeRates/QueryFXCurrencyRate/brncd/{brncd}/ccy1/{ccy1}/ccy2/{ccy2}

The input for the GET services is passed as a part of the URL and if more than one input needs to be passed they should be separated by a forward slash (/). Apart from passing the customer number as a part of the URL, the services also expect a few header parameters to be passed to the service. The following are the header parameters passed:
  1. UserId : OBTR login user Id.
  2. Branch : The bank branch to which the user belongs.
  3. MsgId : A alpha-numeric input from the consumer.
  4. Source : Source of the request whether it is OBTR or an external system.
  5. Content-Type : This mentions the format of the input /output. Since we are using the JSON format we give the content-type as application/json.
  6. Entity : Entity ID
UserId, password and msgId are for authenticating the user accessing the service.

The list of services are discussed in detail in the following topics.

This topic contains following sub-topic: