Securities View API provides access to the Swift Securities View service, giving you visibility on the end-to-end securities settlement transaction flow. To learn more about this API, see Securities View API Overview. In this section you will find the technical implementation details on how to integrate with Securities View API.
Refer to the Securities View API Reference to help you integrate the API.
Understanding the business rules are necessary when integrating with Securities View API. These rules are explained in the Securities View rulebook in the Swift Knowledge Centre.
Looking for a faster and easier way to integrate? Consider using one of the developer tools designed to simplify the consumption of API-based services available on the Swift platform. Build your application with Swift SDK to help you with lower-level application plumbing, which includes authentication, authorisation, signing and error handling. Alternatively, consider using Swift Microgateway to configure, monitor all API calls you make on Swift and capture inbound API requests. Finally, Swift zero-footprint is an option that provides reference implementations so that you can create your own SDK or utilities.
Not sure which tool is right for you? Try the connectivity option selector to get recommendations from our expert. After you select a tool, try setting it up in the API sandbox (available over the Internet) to quickly get started.
Securities View API sandbox returns static sample responses and does not contain any application logic. This sandbox is recommended for developers who want to learn and understand the authentication method JWT Bearer grant type by testing it out with a self-signed certificate over the Internet. This sandbox also ensures that the application generates valid requests and can consume valid responses conforming to OpenAPI specifications. It is also recommended for developers who are trying to set up the developer tools aimed to make integration easier.
You can view, fork or download the Postman collection which includes authentication API calls and sample Securities View API calls. Also refer to access sandbox where dedicated sandbox credentials are provided. To start testing in the sandbox, create an app and select Securities View API.
Swift Pilot environment closely resembles the Live environment, and it is intended to fully qualify your API integration. Make sure you are subscribed to Securities View. Follow the steps below to access the Securities View API Pilot testing environment.
Create a dedicated app for testing in the Pilot environment and select Securities View API from the list of API products. Inside the app are consumer-key and consumer-secret which are the application credentials used to identify the application calling the API. After creating the app, promote the app to the Pilot environment.
Securities View API supports the use of Business certificates and Channel certificates when signing the JWT in the authorisation API call. After creating the certificate, assign the RBAC role swift.secmon.api!p to the certificate.
This step should be completed by a security officerClick to learn more about SWIFTNet PKI Security Officer registration in the Knowledge Centre..
After completing the steps above, you now have the credentials you need to access the Securities View API in the Pilot environment. Refer to Authentication to learn how to use the credentials you created above to start testing your integration with this API in Pilot.
After successfully testing the Securities View API in Pilot, follow the steps below to start using this API in Live.
Promote the app you created to the Live environment or create a new app for the Live environment. If you decided to create a new app, select Securities View API from the list of API products. After the app is created, promote the app to the Live environment.
You should promote the app to Pilot first and then Live.
Follow the same process for creating the certificate for Pilot testing. Securities View API supports the use of Business certificates and Channel certificates when signing the JWT in the authorisation API call. After creating the certificate, assign the RBAC role swift.secmon.api to the certificate for Live.
This step should be completed by a security officerClick to learn more about SWIFTNet PKI Security Officer registration in the Knowledge Centre..
Swap out the credentials you used for Pilot with Live credentials and start using the Securities View API in your Live applications. When in doubt, refer to Authentication to learn how to use your Live credentials to access this API in Live.