Connect your own systems to TransferGo and retrieve your account activity automatically, so there's no need to log in to check.
1. What is the TransferGo Business API and what can I do with it?
We're adding a new way to connect with TransferGo: the TransferGo Business API. This lets your business retrieve your account activity directly from your own systems, so you don't need to log in to TransferGo Business every time you want to check your payments.
This is especially useful if:
- You reconcile payments regularly: pull your transaction data straight into your own accounting or ERP (enterprise resource planning) software.
- You have a developer team: connect once, and let your systems do the checking for you.
Right now, this covers retrieving your account activity only. The ability to send payments through the API is coming later this year, and we'll let you know when it's ready.
For the full picture of what the API can do, see the developer documentation.
2. How do I start connecting my systems to the TransferGo Business API?
- Open API Integrations: Log in to TransferGo Business and click API Integrations in the left-side menu.
- Start the connection: Click Agree & create API connection.
- Accept the terms: Creating an API connection requires accepting our updated Terms and Conditions.
Not the account Owner? You won't be able to confirm this step yourself, so see the next article for what to do.
3. Approving an API connection as the account Owner
If a team member starts setting up an API connection but isn't the account Owner, they'll need your approval before it can go live.
- Receive the confirmation link: Your team member will send you a link to confirm the connection.
- Review and accept: Open the link and accept the updated Terms and Conditions.
- Done: Once confirmed, your team member can continue setting up the certificate and connecting their systems.
4. How do I generate my certificate and connect?
Once your connection is confirmed, you'll set up a client certificate that lets your systems connect securely, then use it to get an access token.
Main facts to know:
- Your private key is generated on your own machine and never leaves it.
- Certificates are valid for 1 year.
- Access tokens last 5 minutes, so cache and reuse each one rather than requesting a new one for every call.
- Uploading your certificate signing request (CSR) is a sensitive step, so you'll be asked to confirm it with your password.
How to do it:
- Open API Integrations and follow the How to connect guide for your operating system (Windows or macOS/Linux).
- Follow the steps shown to generate your certificate, then get an access token and test your connection.
Stuck partway through? There's an I need help link on the setup screen.
For the exact commands, certificate details, and token requests, see the Authentication and Authorization guide.
5. How do I manage my API certificates?
You can manage your certificates any time from API Integrations.
A. Downloading your certificate
- Go to API Integrations.
- Find your certificate in the table and click Download .CRT.
B. Adding a secondary certificate
- Go to API Integrations.
- Click Add secondary certificate.
This is useful if you want a backup certificate ready before your primary one expires.
C. Revoking a certificate
- Go to API Integrations.
- Find the certificate you want to remove and click the revoke icon next to it.
- Confirm the removal.
Once revoked, that certificate can no longer be used to connect, so make sure your systems aren't relying on it first. If you revoke your primary certificate, your secondary certificate automatically becomes the primary one.
Main fact to know: certificates are valid for 1 year. To rotate without downtime, add a secondary certificate ahead of your primary one's expiry, switch your systems over to it, then revoke the primary.
For more on expiry and rotation, see Certificate expiration and rotation.
6. What can I retrieve through the TransferGo Business API?
Once connected, you can pull your account activity directly into your own systems. This covers transfers and top-ups, as well as currency exchanges, savings deposits and withdrawals, interest and balance adjustments.
For each transaction, you'll get details like its status, date and time, amounts and currencies, fees, your references, and sender and payee details, with card numbers masked for security.
Results are paginated and filterable, so large histories load in manageable chunks.
This is read-only for now: you can retrieve data, but you can't send payments through the API yet. That capability is planned for later this year.
For the complete list of fields, statuses, and filtering options, see the transactions reference.