T2S PoC APIs

Previous page Transaction Screening API Reference

T2S PoC APIs enable T2S actors to get settlement instructions information and to access cash service information. To learn more about the APIs, see Cash Queries PoC API overview and Settlement Instructions PoC API overview. In this section, you will find the technical implementation details on how to integrate with the APIs.

OpenAPI specification

Refer to the following OpenAPI specifications to integrate the APIs.

Choose developer tools

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 to help you with lower-level application plumbing, which includes authentication, authorisation, signing and error handling. Alternatively, consider using to configure, monitor all API calls you make on Swift and capture inbound API requests. Finally, is an option that provides reference implementations so that you can create your own SDK or utilities.

Swift SDK

Swift Microgateway

Swift zero-footprint

Not sure which tool is right for you? Try the connectivity option selector to get recommendations from our expert.

Test T2S PoC APIs in Pilot

This API is only available for testing in the Swift Pilot environment as this API is provided for proof-of-concept (PoC) and evaluation purposes only. It is not a production-ready or generally available (GA) service. Follow the steps below to proceed with testing this API in the Pilot environment.

Step 1: Submit e-order

Info

E-order process can take up to 14 days to complete, we suggest submitting the e-order in advance to avoid delays in accessing the service.

1Sign in to Swift.com with ordering priviledge.

2Order the T2S API pilot testing service via the e-order form.

Step 2: Create an app for Pilot

1Sign in to Swift Developer Portal via the option "Sign in with swift.com".

2Create a dedicated app for testing in the Pilot environment and select T2S PoC APIs 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.

3After creating the app, promote the app to the Pilot environment.

Info

The request to promote an app can take up to 5 business days, we suggest submitting the request in advance to avoid delays in accessing the service.

Step 3: Create Certificate & assign RBAC role for Pilot

Caution

This step should be completed by a security officerClick to learn more about SWIFTNet PKI Security Officer registration in the Knowledge Centre..

1T2S PoC APIs support the use of Business certificates and Channel certificates for signing the JWT in the authorisation API call.

2After creating the certificate, assign the RBAC role t2s.euc2tst!p to the certificate.

Step 4: Get authorization from 4CB to access data

If you have created a new Swift PKI certificate as indicated in the step above and this certificate has a different Distinguished Name (DN) compared to the ones already provided and stored in the ESMIG reference data platform, please contact 4CB for registration.

Step 5: Making your first test API call in the Pilot environment

After completing the steps above, you now have the credentials you need to access the T2S PoC APIs 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.