FINS Salesforce Financial Experience API - Implementation Template
home
This API implementation template is a component of MuleSoft Accelerators, which accelerate the implementation of essential integration use cases.
The solution includes pre-built APIs, connectors, and integration templates that help unlock business-critical data from external systems and guide you in adopting best practices synthesized from thousands of customer implementations. Use these assets as is or extend them to meet your company’s unique needs.
Overview
This integration template implements the FINS Salesforce Financial Experience API specification. It supports the following functionalities:
- Triggers the customer sync process
- Submits the loan application for processing
- Validates postal address
Important: This API sets the CORS headers on the response to enable it to be accessed from a Salesforce Light Web Component. You may also choose to apply the CORS policy to this API in API Manager instead.
Getting started
The Getting Started with MuleSoft Accelerators guide provides general information on getting started with the accelerator components. This includes instructions on setting up your local workstation for configuring and deploying the applications. |
Once your workstation has been set up and the application template imported into Anypoint Studio, proceed with the Prerequisites section.
Prerequisites
This implementation template has the following dependencies:
- FINS Bank Loans Process API
- Global Party System API
- Global Financial Account Process API
- FINS Core Banking Poller Process API
- FINS Address Validation System API
API dependencies
The following table lists all endpoints used by this API.
API name | Endpoint | Action |
---|---|---|
FINS Core Banking Poller Process API | post:/pollers/customers | Trigger Poller |
Global Financial Account Process API | get:/accounts/{accountId}/externalIds | Get External IDs using AccountId |
Global Financial Account Process API | get:/cards/{cardId}/externalIds | Get External IDs using cardId |
Global Party System API | get:parties/{contactId}/externalIds | Get External IDs using contactId |
Global Party System API | get:/partyRoles/{customerId}/externalIds | Get External IDs using customerId |
FINS Address Validation System API | post:/validators/postalAddresses | Post Address Validation |
FINS Bank Loans Process API | post:/loans/applications | Submit Loan Application |
FINS MDM Accounts System API | get:/transactions/{transactionId}/externalIds | Get External IDs using transactionId |
Deployment
Each Accelerator implementation template in Exchange includes Bash and Windows scripts for building and deploying the APIs to CloudHub. These scripts depend on repositories, global settings, deployment profiles, and associated properties configured in the Maven settings.xml
file.
For additional details, please refer to the Application Deployment section of the Getting Started Guide.
Preparation
Ensure the Maven profile CloudHub-FINS-DEV
has been properly configured in your settings.xml
file. In particular, make sure the common properties for your environment have been provided (e.g., Anypoint Platform client ID and secret).
Required property overrides
At a minimum, the following properties must be customized to reflect the target deployment environment.
Property Name | Description |
---|---|
api.autodiscoveryID | Required if using API Manager to secure this API |
bank-loans-prc.host | Bank Loans Process API HostName |
bank-loans-prc.port | Bank Loans Process API Port |
bank-loans-prc.ping-path | Bank Loans Process API Ping path |
bank-loans-prc.loans-path | Bank Loans Process API Loans path |
global-party-sys-api.host | Accelerator MariaDB Global Party System API HostName |
global-party-sys-api.port | Accelerator MariaDB Global Party System API Port |
global-party-sys-api.pingPath | Accelerator MariaDB Global Party System API Ping path |
global-finacct-prc-api.host | Global Financial Account Process API HostName |
global-finacct-prc-api.port | Global Financial Account Process API Port |
global-finacct-prc-api.ping-path | Global Financial Account Process API Ping path |
core-banking-poller-prc.host | Core Banking Poller Process API HostName |
core-banking-poller-prc.port | Core Banking Poller Process API Port |
core-banking-poller-prc.ping-path | Core Banking Poller Process API Ping path |
core-banking-poller-prc.poller-path | Core Banking Poller Process API Poller path |
address-validation-sys-api.host | Address Validation System API HostName |
address-validation-sys-api.port | Address Validation System API Port |
address-validation-sys-api.ping-path | Address Validation System API Ping path |
Testing
Use Advanced Rest Client or Postman to send a request over HTTPS. The template includes a Postman collection in the src/test/resources
folder. Update the collection variable(s) after successful import.
Additional resources
- The Data mappings tab describes how the request and response data structures are mapped between the API interface and the downstream APIs.
- Refer to the Accelerators documentation home for more information about the MuleSoft Accelerators.