Make calls to SWIFT APIs is easy using SWIFT SDK. All you need to do is add the SWIFT SDKs as dependency when building your Java application through Maven or Gradle.
We built this demo Java application with Maven to show you how we are using it to make calls to SWIFT gpi APIs in the API Sandbox.
- Java 17 and above
- maven 3.5.* and above
Download SWIFT SDK from SWIFT Developer Portal, login is required for download.
Unpackage the zip file and install the dependency in your local .m2 repository.
$ install.sh
Download SWIFT Security SDK from SWIFT Developer Portal, login is required for download.
Unpackage the zip file and install the dependency in your local .m2 repository.
$ install.sh
In cases where the SDK version in the pom.xml file do not match the ones available on SWIFT Developer Portal, please run the following command. The versions plugin will update your pom file with the latest available in your local repository.
After installing the SDK packages, navigate to where you have cloned this project and execute these in the same directory as the pom.xml file.
$ mvn versions:use-latest-versions -Dincludes=com.swift.commons.oauth:swift-security-sdk
$ mvn versions:use-latest-versions -Dincludes=com.swift.apisdk:swift-sdk-swagger
Update config/config-swift-connect.yaml with your application credentials, consumer-key & consumer-secret. Obtain from SWIFT Developer Portal by creating an app.
To use forward proxies update config/config-swift-connect-fp.yaml with your application credentials, consumer-key & consumer-secret and forward proxy information. Obtain from SWIFT Developer Portal by creating an app.
$ mvn clean install
$ java -Dlog4j.configuration=file:config/log4j.properties -jar target/gpi-v5-demo-app-jar-with-dependencies.jar config/config-swift-connect.yaml
To use forward proxies:
$ java -Dlog4j.configuration=file:config/log4j.properties -jar target/gpi-v5-demo-app-jar-with-dependencies.jar config/config-swift-connect-fp.yaml
The keystore (conf/keystore.jks) has these several entried that may need renewing when the Sandbox certificate is renewed:
- globalsign_root_ca_r3, 18 Oct 2022, trustedCertEntry, Sandbox server root ca
- globalsign_rsa_ov_ssl_ca_2018, 18 Oct 2022, trustedCertEntry, Sandbox server sub ca
- sandbox_pub, 18 Oct 2022, trustedCertEntry, Sandbox server cert. Potentially not needed given its roots are present (see above)
- selfsigned, 18 Jun 2020, PrivateKeyEntry, Demo client key