# Migrate from TRDS

import { Badge } from "zudoku/ui/Badge"

The Transact Remote Data Service (TRDS) is the predecessor to the unified Transact API and consists of several
isolated services. These services are now largely deprecated and will be eventually removed.

## TRDS services

The current status of the various TRDS services is summarised in the table below.

| Legacy Service                                                               | Authorisation      | Service Status                                  | Removal Date       | Transact API Equivalent
| ---------------------------------------------------------------------------- | -------------------| ----------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------- |
| [Account Opening](https://documenter.getpostman.com/view/8344085/2sAYX9ogTh) | OAuth              | <Badge variant="destructive">DEPRECATED</Badge> | 31 December 2026   | [Prepopulate a Personalised Illustration](/api/account-opening#prepopulate-a-personalised-illustration)  |
| [Advisers](https://documenter.getpostman.com/view/8344085/2sAYX9ogTh)        | OAuth              | <Badge variant="destructive">DEPRECATED</Badge> | 31 December 2026   | [Get advisers](/api/advisers#get-advisers)                                                               |
| [Firms](https://documenter.getpostman.com/view/8344085/2sAYX9ogTh)           | OAuth              | <Badge variant="destructive">DEPRECATED</Badge> | 31 December 2026   | [Get firms](/api/firms#get-firms)                                                                        |
| [Remuneration](https://documenter.getpostman.com/view/8344085/2sAYX9ogTh)    | OAuth              | <Badge variant="destructive">DEPRECATED</Badge> | 31 December 2026   | [Get remuneration](/api/remuneration#get-remuneration)                                                   |
| Valuation                                                                    | TRDS Password      | <Badge variant="destructive">DEPRECATED</Badge> | 31 December 2026   | [Get valuations](/api/valuations#get-valuations)                                                         |
| Transaction                                                                  | TRDS Password      | <Badge variant="default">SUPPORTED</Badge>      | -                  | -                                                                                                        |

:::info

All Transact API endpoints require authorisation via OAuth.

:::

## Migrating to Transact API

This section discusses changes to be aware of when migrating your integration.

### OAuth

Along with the Transact API release, Transact's OAuth endpoints have been moved to a separate service at
https://auth.transact-online.co.uk. **The old URLs will be removed on 31 December 2026.**

To continue using Transact's OAuth flow, the following URLs must be updated in your code.

| Endpoint               | Old URL                                        | New URL                                  |
| ---------------------- | ---------------------------------------------- | ---------------------------------------- |
| Authorisation Endpoint | https://user.transact-online.co.uk/Oauth       | https://auth.transact-online.co.uk       |
| Token Endpoint         | https://user.transact-online.co.uk/Oauth/Token | https://auth.transact-online.co.uk/token |

:::danger

Refresh tokens obtained from the old `user.*` URLs will continue to function and are usable with the
new `auth.*` URLs, however it is important to note that `Read` and `Stage` scopes are used solely by the old TRDS endpoints. Preexisting tokens with only
these scopes are not usable with Transact API endpoints; **users will need to re-authorise in order to grant the required scopes**.

:::

### Valuation

The TRDS "Valuation" service has been superseded by the Transact API's [Get valuations](/api/valuations#get-valuations)
endpoint, which has been redesigned and standardised to follow REST API principles.

The new endpoint also improves visibility of new wrappers and wrapper state transitions.

To migrate your existing integration to the Transact API, changes specific to your software and use case
will be required, including **implementing OAuth**.

The following resources may be helpful when planning your migration:

- [Getting Started](../getting-started/overview.md) guide
- [Get a Portfolio Valuation](valuation.md) guide
- [Get valuations](/api/valuations#get-valuations) endpoint documentation

### Account Opening

The TRDS "Account Opening" service has been superseded by the Transact API's
[Prepopulate a Personalised Illustration](/api/account-opening#prepopulate-a-personalised-illustration) endpoint,
which has an identical schema.

1. Update the request URL to point to the Transact API's endpoint.
2. Add the `Transact-Api-Version: 2026-05-12` request header.
3. Update error handling to account for the Transact API's new [error structure](../advanced/errors.md).

:::info

Unlike the TRDS Account Opening service, the Transact API
[Prepopulate a Personalised Illustration](/api/account-opening#prepopulate-a-personalised-illustration) endpoint requires the
`investor-illustration-profile` [scope](../advanced/scopes.md).

:::

See also the [Open an Investor Account](account-opening.md) guide, which walks through using this functionality to
open an investor account.

### Remuneration

The TRDS "Get Latest Remuneration Statement" and "Get Historical Remuneration Statement" endpoints have been superseded
by the Transact API's single [Get remuneration](/api/remuneration#get-remuneration) endpoint, which
has:

- an **updated schema** - renamed parameters, renamed response properties and redefined enum definitions
- optional parameters for date range filtering (to achieve the equivalent of the TRDS "Get Historical Remuneration Statement" functionality).

To migrate your existing integration to the Transact API:

1. Update the request URLs to point to the Transact API's endpoint.
2. Add the `Transact-Api-Version: 2026-05-12` request header.
3. Update request and response handling to account for the new schema.
4. Update error handling to account for the Transact API's new [error structure](../advanced/errors.md).

:::info

Unlike the TRDS Remuneration service, the Transact API
[Get remuneration](/api/remuneration#get-remuneration) endpoint requires
the `transaction.read` and `entity.read` [scopes](../advanced/scopes.md).

:::

### Advisers and Firms

The TRDS "Advisers" and "Firms" endpoints have been superseded
by the Transact API [Get firms](/api/firms#get-firms) and [Get advisers](/api/advisers#get-advisers) endpoints, which
have updated schemas in order to support [paginated](../advanced/pagination.md) responses.

To migrate your existing integration to the Transact API, for each endpoint:

1. Update the request URL to point to the Transact API's endpoint.
2. Add the `Transact-Api-Version: 2026-05-12` request header.
3. Update request and response handling to account for the new schema that includes [pagination](../advanced/pagination.md).
4. Update error handling to account for the Transact API's new [error structure](../advanced/errors.md).

:::info

Unlike the TRDS Advisers and Firms services, the Transact API [Get firms](/api/firms#get-firms) and
[Get advisers](/api/advisers#get-advisers) endpoints require the
`entity.read` [scope](../advanced/scopes.md).

:::