API access

To begin development you will need API keys to the BankTech Sandbox API which can be requested by signing up for an account through our or by contacting our if you already have an account. API keys are issued per environment and per user.

Environments:

(for development, testing and demonstration)
(for live instructions)

The Sandbox environment allows users to utilise all of our services, subject to fair usage policy, and obtain simulated collection and live verification and authentication results. These Sandbox services are normally provided free of charge to new users with API keys looking to get to know our product.

API keys:

ClientKey: the system-assigned private identifier for your user account
ClientSecret: the system-assigned private password

You can also to have a service user created for the purposes of issuing an API key that is not associated with a real person and instead represents your organisation's integration solution's services and workers. For example, one could create a separate service user for various departments or entities.

It is critical that you do not disclose your ClientKey or ClientSecret to anyone – even those in your own organisation. Please don't include it in emails or other communication to us either. If you have inadvertently exposed your API keys, please get in touch with our so that we can verify your identity and reissue your credentials to keep your account safe.

To use our API, you will need to authenticate yourself by using your API key to obtain a token. You must have a valid token to make requests. Tokens are valid for a 15 minutes. They can be extended before expiry, otherwise a new token must be created.

The quickest way to get started is to explore the rest of the developer guide to familiarise yourself with the major feature workflows. Thereafter you can simply visit the Sandbox environment's to authenticate yourself, obtain a token and try out some of our methods.

If you have entered your details correctly, you should have a 200 (successful) status code response and a token issued to you as part of the response. You can now authorise yourself with this token, but keep in mind it will expire in 15-minutes and you may need to refresh the token's expiry or get a new token.

If this token was correctly entered, you are now authorised and can use our methods. Happy exploring!

For those more interested in a code-driven approach, the below outlines two very simple cURL examples of how you could achieve the same result as above without using the Swagger interface:

 // Obtain an OAuth 2 bearer token with your API key credentials
 
 curl -i -X POST https://api.sandbox.bank.tech/auth/get-token -H "Content-type: application/json" -d "{'clientKey': 'string','clientSecret': 'string'}"

// Use the bearer token authentication scheme in the header of your next request

 curl -i -X GET https://api.sandbox.bank.tech/collections -H "Content-type: application/json" -H "Authorization: Bearer {TOKEN}" -d "{'ForDateStart;': '2021-01-01', 'ForDateEnd': '2021-12-31'}"
 
 // Remember, this token is only valid for 15 minutes and must be renewed or extended.

PreviousAPI integration NextMethods

Last updated 3 years ago

Was this helpful?

// Obtain an OAuth 2 bearer token with your API key credentials curl -i -X POST https://api.sandbox.bank.tech/auth/get-token -H "Content-type: application/json" -d "{'clientKey': 'string','clientSecret': 'string'}" // Use the bearer token authentication scheme in the header of your next request curl -i -X GET https://api.sandbox.bank.tech/collections -H "Content-type: application/json" -H "Authorization: Bearer {TOKEN}" -d "{'ForDateStart;': '2021-01-01', 'ForDateEnd': '2021-12-31'}" // Remember, this token is only valid for 15 minutes and must be renewed or extended.