What's New

July 2025

We've expanded support for custom tabs to additional locations. You can now use them in the following views:
- tasks list
- orders list
- projects list
- reports list

To facilitate the management of large translation requests, batching support has been added for MT provider apps. This update includes the introduction of a new parameter, extensions.configuration.segmentBatchSize, which can be added to your descriptor, along with a new error response featuring status code 413 on the translation endpoint.
A new option has been introduced on the app registration page, allowing users to designate their app for development purposes by selecting a checkbox.

We have officially rebranded from RWS Language Cloud API to Trados Cloud Platform API. All references to our previous brand name will now reflect our new identity, Trados.

This release introduces support for building apps that work across multiple regions. Existing apps that are already developed and in use will continue to function but will be restricted to the EU region until they are updated.
To help you make the required changes for multi-region support, we've provided a new guide, which you can access here.
Updated blueprints and sample projects are also available to get you started.

With this release we deliver a new extension point designed to allow developers to extend and customize the UI elements of our platform. This extension point is being released as BETA. For more details see this page.
We unified the Preview documentation pages into a single comprehensive page. We have introduced a new version, known as V2, of our Preview APIs.
We extended the information available under Verification Provider page. We have introduced a new version, known as V2, of our Verification APIs.
You can now add comments to Submit Task Outcome for the automatic task extensions.

With this release, we have migrated from the Add-Ons concept to Apps. This significant first step sets the stage for expanding this concept to multiple areas that facilitate integrations.
Registered Add-Ons are backward compatible with the new Apps and can be used as is.
A major improvement is that an App can now declare the list of webhooks it needs in the descriptor and listen for webhook notifications.
The migration guide from an Add-On to an App is available here.

We added support for dropdown lists to the app configuration. You can now define a set of values in the descriptor's configurations section as an array of strings via the options field. The user will see these values in a dropdown menu in the edit configuration panel.

With this release we introduced a folder identifier where the translation engines will be added. This can be used to filter the engines by folder.
We also added recommendations on best practices for a secure application development.
We made additional smaller improvements and corrections to our documentation.

We added details for the engineId, projectId, sourceFileId and targetFileId parameters of the Translate endpoint.
We updated the Registering the app page.

We introduced requirements that become mandatory for all future apps, namely: acceptance of Terms & Conditions and the Privacy Policy, along with the provisioning of the app's release notes, documentation link and the developer's contact details, starting with descriptor version 1.3.
We published newer blueprints for both Java and .NET.
We made available headers for developers to implement custom functionality based on the current version of the installed apps: appVersion, extensionPointVersion and extensionId.
Added projectId, sourceFileId and targetFileId on the translate request.

We published new pages with our recommendations for implementing Dynamic Preview.

We made available app samples for both .NET and Java in GitHub, to allow integrators to get familiar with our framework extension possibilities.
We published a new page with Technical Requirements And Best Practices.