Temenos Digital
R24 AMR | Min(s) read

Arrangement

Arrangements API is used to get the customer’s account related information. This information includes Account details, Balance and other interest related information. Arrangement APIs are connected to other Micro services or T24 to fetch the customer’s account details based on the user requirement.

The user must install and integrate the Microservice app with the base application before consuming the Arrangement API. For more information, click here.

Name Description Introduced In
saveActionsPermissionsInCache This API stores the actions and permissions for all the accounts in cache. When getAccountFeaturesAndPermissions is called multiple times, response of individual call is available in cache, this service picks the individual calls actions and stored them in consolidated key. Input for this is starting coreCustomerid passed in each call to getAccountFeaturesAndPermissions. 2023.07
getAccountFeaturesAndPermissions This API retrieves the account level actions and permissions for all the accounts of the logged in user. As a part of getList we get all the features and permissions for each account, to improve the performance this is separated from getList and created a new service to get the data. If this user has more than 10 corecustomer ids, this has to be called in a loop by passing 10 core customer ids in one call 2023.07
getCoreCustomerIdsandAccounts This API helps when output of this service decides whether Customer dashboard need to be displayed or Account dashboard need to be displayed. 2023.07
getList with action as false This API returns all the accounts of that user including accounts of different core customers but with out account level actions. 2023.07
getList with membershipid This API returns all the accounts of only that core customer id with actions. 2023.07
getList This API retrieves all the accounts that are associated with the customer, such as savings, deposit, and credit accounts from the associated microservice or Transact. The fetched accounts are displayed to the customer based on the account type. This API gets invoked immediately after a customer signs-in to the account. 2020.04
     
     
getDetails This API retrieves the details of a particular account. This API in invoked from client when the user selects a particular account. 2020.04
getAccountsForAdmin Retrieves all the accounts for an administrator, based on the User ID. The User ID is a unique ID that gets generated for every user after a successful login. This API provides an admin based access to accounts 2021.01
getAccountsByCustomerIDForAdmin Retrieves all the accounts for an administrator, based on the Customer ID . The Customer ID is a unique ID specific to a customer. This API provides an admin based access to accounts. 2021.01
createView This API creates a new custom view. 2021.07
getView This API fetches the list of custom view for accounts. 2021.07
updateView This API updates the data for the custom view. 2021.07
deleteView This API deletes the custom view. 2021.07
accountsPreview This API retrives the list of custom views for an account. 2021.10
Object Data Model This Object Data Model describes the parameter name and other attribute details for Arrangement.  

Click here to view the object data model.

In this scenario, the getList API is used to fetch the account list immediately after you log in, whereas the GetAccountDetails API is used to fetch the details of a specific account in the list. The output response of the getList and getAccountDetails APIs is the same as both the APIs are pointing to the same endpoint (Microservice). Therefore, when you invoke the getList API, the output response of this API contains the account details also.

In this topic

Copyright © 2020- Temenos Headquarters SA

Published on :
Thursday, May 30, 2024 1:07:42 PM IST