TRANSACT API – OVERVIEW
Many adviser tools now connect directly to platforms like Transact.
These connections are often referred to as integrations. In simple terms, an integration allows two systems advisers already use to securely share information with each other — for example, your Customer Relationship Management (CRM) pulling portfolio values from Transact, or pre‑filling a Transact portfolio application using client data you already hold in your CRM.
The Transact API is the technology that makes these integrations possible.
What is the Transact API?
The Transact API is a secure, modern way for approved systems to connect directly with the Transact platform on your behalf.
Instead of logging into Transact Online and re‑keying information, adviser software can:
- Send data to Transact
- Retrieve data from Transact
In practical terms, it acts as a bridge between Transact and adviser technology such as:
- CRMs and back-office systems
- Financial planning and portfolio tools
- Adviser-built proprietary systems.
The API is built using widely adopted industry standards and represents the long‑term replacement for the legacy Transact Remote Data Service (TRDS).
Why the Transact API matters to advisers
API‑based integrations make a meaningful difference to day‑to‑day advice workflows:
- Less re-keying, fewer errors – Client and portfolio data can flow directly between systems.
- Faster servicing – Common tasks such as valuations and account opening can be built into tools you already use.
- Better client experience – Less admin time means more time focused on clients.
- Future capability – The API is built to offer future services such as model management and instruction submission.
Crucially, the adviser remains in control. Systems can only access data or perform actions where the advisers have explicitly authorised them to do so.
Who can use the Transact API?
Depending on the service, access to the Transact API may be used by:
- Adviser firms (including those using proprietary systems)
- Adviser networks
- Third-party software providers acting on behalf of the adviser.
In all cases, access is subject to formal registration, contractual terms, and explicit authorisation granted within Transact.
What services are available today?
The Transact API already supports a growing set of live services.
To get started, you’ll need to give your software provider permission to access Transact data and/or perform the required actions. You can find guidance on how to do this here.
1. Account opening
The software provider can pre‑populate a Transact Personalised Illustration using client data the adviser already holds elsewhere. This helps to:
- Reduce manual data entry
- Minimise errors
- Speed up onboarding
After pre‑population, the adviser moves into Transact Online to review the details, generate documentation, and complete the application.
How the account opening integration works
|
1
The adviser initiates a Transact account opening integration
The adviser initiates the opening of a Transact portfolio from within their CRM/back office, based on client information stored in the CRM. This could be initiated by clicking a Create Illustration button.
|
|
2
The CRM determines the adviser’s Transact number
The adviser’s CRM calls the Transact API to retrieve the adviser’s Transact number, which is required to generate an Illustration.
|
|
3
The adviser reviews information
The adviser reviews the applicants’ information (and potentially enriches it) within their application, before it is sent to Transact.
|
|
4
The adviser’s CRM creates a Transact Personalised Illustration
With the adviser’s Transact number and the applicants’ information, the CRM calls the Transact API, which creates a Transact Personalised Illustration on Transact Online and stores both the illustration, and data, that can later be used to prepopulate a Guided Application.
Click here to see the data points available; while many of them are optional, it is best practice for software providers to utilise all of them to minimise re-keying for advisers. A unique link is returned to the CRM that can be used by advisers to view and modify the relevant illustration within Transact Online. |
|
5
The adviser proceeds to Transact Online to complete the process
Following the link (for example, in the form of a View Illustration button), the adviser accesses their illustration within Transact Online, prefilled with all the information the application supplied. The adviser may download the illustration, make it available to the applicants, and go on to complete the application using Transact Online.
|
2. Valuations
The software provider can retrieve end‑of‑day portfolio valuations at scale, including:
- Wrapper details
- Holdings and values
- Wrapper status (open, closing, closed)
This is widely used for client reporting, reconciliation, and adviser dashboards.
3. Remuneration data
The software provider can retrieve remuneration statements, supporting reconciliation of expected versus paid remuneration without manual exports.
Transaction data (currently via TRDS)
Many adviser systems already retrieve transaction data from Transact, for example to support reporting such as contributions and withdrawals to clients.
Today, this service is provided via the legacy Transact Remote Data Service (TRDS) and continues to be fully supported.
Over time, this functionality will be migrated to the Transact API, with the API‑based service planned to be available from 2027.
Tip: Many adviser software providers already integrate with Transact. Click here to view the table of current integrations with software providers/CRMs.
If your software provider doesn’t integrate it’s worth checking with them, it could save you time and reduce re-keying in day-to-day work.
What is planned for the future?
New API services are introduced incrementally and in a controlled way.
Planned developments include:
- Model management and instructions (Models API) – Allowing DIMs and other authorised parties to submit instructions to Transact via the API.
- Broader document access – Including client reports and platform documentation where appropriate.
- Expand data coverage – Additional event, status, and lifecycle data across wrappers and clients.
Over time, advisers, through their CRM will not just read Transact data but be able to instruct Transact.