Forums - Recent Threads

RE: API call

Nick Date — Mon, 13 Apr 2026 09:32:20 GMT

You can create a Service User in Users -> Service Users

If you can't see this, then you may not have the necessary entitlement. We cannot give this sort of information out on a public forum, so please raise a support case, and we will be happy to help.

API call

Nzhdeh Barseghyan — Wed, 08 Apr 2026 08:49:26 GMT

Hi!
I am a developer building a standalone automation service using the Trados Public API. I need to set up a Service User for OAuth2 Client Credentials authentication, but I cannot locate the 'Service Users' management area in my current dashboard.

Can you please:
Point me to the exact location of Service User management for my tenant?
Confirm if my current subscription tier supports Public API access and the creation of Service Users?
Verify if OCR (Optical Character Recognition) is enabled for my account's file-type configurations so I can analyze JPG/PNG files?

Thank you in advance.

RE: API call

Nzhdeh Barseghyan — Mon, 13 Apr 2026 06:01:02 GMT

Hi Laszlo David , here is my tenant ID - xxxxxxxxxxxxxxxx.

Thank you in advance.

RE: API call

Laszlo David — Fri, 10 Apr 2026 10:42:23 GMT

hi Nzhdeh Barseghyan , can you provide some details? account/tenant id?

Data bridge does not support "contains" in filter

Laurent Pierret — Mon, 30 Mar 2026 07:39:34 GMT

Good morning,

Although described here: developers.rws.com/.../OData-Query-Guide.html, the data bridge does not support the "contains" function in filter. See attached screenshot: the error says "Method are not allowed".

Thank you for your guidance.

Potential outage 24-25 FEB 2026

Evgenii Samarin — Thu, 19 Mar 2026 13:07:25 GMT

Hello RWS team! Our client got an error in workflow tasks. Based on our logs/opentelemetry, there were no requests that we received. Could you please check what happened to the step in the workflow pipeline?

Details about the error received: Task,UNRESPONSIVE,699e01d571231a419a4df3bf

RE: Potential outage 24-25 FEB 2026

Laszlo David — Fri, 20 Mar 2026 12:31:53 GMT

Hi Evgenii:

we can see from the logs:

2026-02-24 19:54:11.210
[Calling extension with id intento-routings-bcm-async-automatictask. Sending a POST request to connectors.inten.to/.../bcmtranslate_async

but there was no callback received for this task in 4hours, so the task was expired

RE: Potential outage at Dec 27th, 10:01–22:30 PST

Laszlo David — Fri, 20 Mar 2026 12:10:14 GMT

The page where outages can be seen is: https://status.cloud.trados.com/

Potential outage at Dec 27th, 10:01–22:30 PST

Evgenii Samarin — Tue, 30 Dec 2025 11:04:49 GMT

Hello RWS team!

We haven't received any requests from the platform for Dec 27th, 10:01–22:30 PST, based on both our and and logs that we can download on my apps tab.

Were there any outages at this time? And is there a place we can track this, like a status page?

How to receive all fields of multiple termbase entries without exceeding URL length limit

Tamas Meszaros — Tue, 24 Feb 2026 13:16:54 GMT

Hi,

I would like to read several termbase entries through the LC rest API, and I would like to query all fields of them.

According to the docu, optional fields are not returned by default, so I have to specify all required fields in the fields parameter. This alone is already very long, ~ 3300 characters:

fields=humanReadableId,languages.language.languageCode,languages.language.englishName,languages.terms.text,languages.terms.systemStatus,languages.terms.termbaseFieldValues.termbaseFieldId,languages.terms.termbaseFieldValues.name,languages.terms.termbaseFieldValues.value,languages.terms.termbaseFieldValues.fieldValueLinks.type,languages.terms.termbaseFieldValues.fieldValueLinks.value,languages.terms.termbaseFieldValues.createdAt,languages.terms.termbaseFieldValues.lastModifiedAt,languages.terms.termbaseFieldValues.createdBy.email,languages.terms.termbaseFieldValues.createdBy.firstName,languages.terms.termbaseFieldValues.createdBy.lastName,languages.terms.termbaseFieldValues.createdBy.anonymized,languages.terms.termbaseFieldValues.createdBy.anonymizedUserName,languages.terms.termbaseFieldValues.lastModifiedBy.email,languages.terms.termbaseFieldValues.lastModifiedBy.firstName,languages.terms.termbaseFieldValues.lastModifiedBy.lastName,languages.terms.termbaseFieldValues.lastModifiedBy.anonymized,languages.terms.termbaseFieldValues.lastModifiedBy.anonymizedUserName,languages.terms.createdAt,languages.terms.lastModifiedAt,languages.terms.createdBy.email,languages.terms.createdBy.firstName,languages.terms.createdBy.lastName,languages.terms.createdBy.anonymized,languages.terms.createdBy.anonymizedUserName,languages.terms.lastModifiedBy.email,languages.terms.lastModifiedBy.firstName,languages.terms.lastModifiedBy.lastName,languages.terms.lastModifiedBy.anonymized,languages.terms.lastModifiedBy.anonymizedUserName,languages.termbaseFieldValues.termbaseFieldId,languages.termbaseFieldValues.name,languages.termbaseFieldValues.value,languages.termbaseFieldValues.fieldValueLinks.type,languages.termbaseFieldValues.fieldValueLinks.value,languages.termbaseFieldValues.createdAt,languages.termbaseFieldValues.lastModifiedAt,languages.termbaseFieldValues.createdBy.email,languages.termbaseFieldValues.createdBy.firstName,languages.termbaseFieldValues.createdBy.lastName,languages.termbaseFieldValues.createdBy.anonymized,languages.termbaseFieldValues.createdBy.anonymizedUserName,languages.termbaseFieldValues.lastModifiedBy.email,languages.termbaseFieldValues.lastModifiedBy.firstName,languages.termbaseFieldValues.lastModifiedBy.lastName,languages.termbaseFieldValues.lastModifiedBy.anonymized,languages.termbaseFieldValues.lastModifiedBy.anonymizedUserName,termbaseFieldValues.termbaseFieldId,termbaseFieldValues.name,termbaseFieldValues.value,termbaseFieldValues.fieldValueLinks.type,termbaseFieldValues.fieldValueLinks.value,termbaseFieldValues.createdAt,termbaseFieldValues.lastModifiedAt,termbaseFieldValues.createdBy.email,termbaseFieldValues.createdBy.firstName,termbaseFieldValues.createdBy.lastName,termbaseFieldValues.createdBy.anonymized,termbaseFieldValues.createdBy.anonymizedUserName,termbaseFieldValues.lastModifiedBy.email,termbaseFieldValues.lastModifiedBy.firstName,termbaseFieldValues.lastModifiedBy.lastName,termbaseFieldValues.lastModifiedBy.anonymized,termbaseFieldValues.lastModifiedBy.anonymizedUserName,createdAt,lastModifiedAt,createdBy.email,createdBy.firstName,createdBy.lastName,createdBy.anonymized,createdBy.anonymizedUserName,lastModifiedBy.email,lastModifiedBy.firstName,lastModifiedBy.lastName,lastModifiedBy.anonymized,lastModifiedBy.anonymizedUserName

The problem is that if I would like to specify e.g. 20 entry IDs like

humanReadableIds=LC6570452991d6c955906daf37&humanReadableIds=LC65707c7082468403c1f9e318&humanReadableIds=LC65707cf5edee745afa957d55&humanReadableIds=LC65707e3082468403c1f9e509&humanReadableIds=LC65707f0382468403c1f9e6de&humanReadableIds=LC657081c1edee745afa98b06d&humanReadableIds=LC6570821682468403c1fd023d&humanReadableIds=LC65708372edee745afa9a787e&humanReadableIds=LC657084e582468403c1fff69a&humanReadableIds=LC657086ec82468403c1015b43&humanReadableIds=LC657087e2edee745afa9cd67a&humanReadableIds=LC657094a0edee745afaadb66b&humanReadableIds=LC65719422edee745afaf41032&humanReadableIds=LC6571958aedee745afaf420dd&humanReadableIds=LC6571962982468403c14c177c&humanReadableIds=LC65719678edee745afaf42829&humanReadableIds=LC6571972cedee745afaf43a28&humanReadableIds=LC6571998bedee745afaf9d717&humanReadableIds=LC65719b8082468403c15526e6&humanReadableIds=LC65719e2dedee745afaf9ed34

then I already get an error like 414 (Request-URI Too Long) ~ the complete GET query is 4275 characters long.

Is there a trick maybe reduce the length? It seems to be kind of waste to use 3300 characters just to express that I would get everything, and having to increase the API calls just because too few space remains for the IDs.

E.g. wildcards would be perfect to use, but AFAIK they are not supported.

thanks,

Tamas

RE: How to receive all fields of multiple termbase entries without exceeding URL length limit

Patrick Andrew Hartnett — Fri, 06 Mar 2026 15:47:16 GMT

hi Tamas Meszaros , The 414 (Request-URI Too Long) is coming from the practical URL length limit enforced by the web server/proxy in front of the API, so very long fields=... + many humanReadableIds=... parameters will hit that limit.

To address the “I just want everything” scenario: we’re currently testing support for a wildcard on the fields parameter (e.g. fields=*) to avoid having to send a very long explicit list. It’s not something we’re ready to officially document/promote yet while we complete validation, but it should help with exactly the use case you described and significantly reduce the URL size.

Until this is fully supported/documented, the reliable workaround is to batch the IDs into smaller groups to keep the request URL under the limit.

I’ll keep you posted as soon as we can confirm the wildcard is fully supported and ready to be documented. Currently tracking yr feedback here SDLCOM-6725 so that I remember to circle back to you when this is supported

RE: How to receive all fields of multiple termbase entries without exceeding URL length limit

Community Jira — Fri, 06 Mar 2026 15:47:16 GMT

Thank you for bringing this to our attention. Our development team will review it in the context of our ongoing projects and priorities. Your understanding and patience as we assess this matter is appreciated. We have recorded the issue in our tracking system under the reference number SDLCOM-6725

RE: Potential outage at Dec 27th, 10:01–22:30 PST

Evgenii Samarin — Fri, 06 Feb 2026 16:18:13 GMT

Hello! We had no such logs, but do you have any information about the potential outage? Do you have a status page where we can track such events?

RE: How to uplad Perfect Match files to the cloud?

Rares Tritean — Fri, 30 Jan 2026 09:08:18 GMT

Yes, please open a ticket IF creating a mapping with the example I've provided does not work.

How to uplad Perfect Match files to the cloud?

André — Mon, 26 Jan 2026 15:04:11 GMT

We recently started using the Trados Cloud platform. I am trying to upload the Perfect Match files (.sdlxliff) via the REST API. Creating a project and uploading the files (via API) works, but Perfect Match is then skipped in the workflow for the files.

Unfortunately, the API reference does not provide quite as much information as it should for the whole thing to work.

I upload the files using the “Add Source File” endpoint: api.eu.cloud.trados.com/.../v1/projects/{projectId}/source-files

The question is, what exactly should the properties look like? Currently, they look like this:

var bilingualUploadProps = Newtonsoft.Json.JsonConvert.SerializeObject(new
{
name = sdlxliffname,
role = "reference",
type = "sdlxliff",
language = sourceLanguageShort
});

Are role and type correct?

Unfortunately, that doesn't seem to be enough.
Do I now have to create a “PerfectMatch Mapping” using the API? If so, how do I do that for the .sdlxliff files? By default the PerfectMatch Mapping want to have "matchingProjects" but we don't have these yet. We want to use the older sdlxliff files.

Thanks for the help.

RE: How to uplad Perfect Match files to the cloud?

André — Fri, 30 Jan 2026 08:28:19 GMT

Sounds like a plan 🙂

This is the trace id:

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

EDIT: The ID is always replaced. How can i provide it? Via Ticket?

RE: How to uplad Perfect Match files to the cloud?

Rares Tritean — Fri, 30 Jan 2026 08:15:00 GMT

Hi,

When creating a new Perfect Match Mapping you should be able to only send the projectId that the mapping will be associated to, i.e: your not started project 6970fa5993d3cd12124d7bbe:

{
  "projectId": "6970fa5993d3cd12124d7bbe"
}

If this step fails, please provide us with a TraceID so we can investigate this further.

Let's unblock this first step then we can continue with the rest of the flow.

- Rares.

RE: How to uplad Perfect Match files to the cloud?

André — Wed, 28 Jan 2026 13:40:59 GMT

Hi Rares,

thanks for your reply.

My first attempt was to upload the sdlxliff files for PerfectMatch via the Add Source File endpoint. But I think this is the wrong way.

After that I tried to create a Perfect Match Mapping.

My body looks like this:

{

"projectId": "6970fa5993d3cd12124d7bbe",

"matchingProjects": [

"6970e3e69e57314fefbc15b5"

]

}

I also tried it without matchingProjects (because I dont want to use other projects for Perfect Match) but I always get this as response:

{

"errorCode": "invalid",

"message": "Input validation error occurred. No further details available.",

"details": []

}

The project with id 6970fa5993d3cd12124d7bbe is not started. Without mappingid I cannot use any of the other Perfect Match endpoints. So right now, I am stuck.

What am I doing wrong?

RE: How to uplad Perfect Match files to the cloud?

Rares Tritean — Wed, 28 Jan 2026 08:50:45 GMT

Hi,

The Perfect Match Mapping flows are detailed in the official documentation.

When working with the Trados Cloud API, you may use the Create Perfect Match Mapping endpoint to create a new one, then Perfect Match should work automatically if conditions above are met.

If you need to provide your own files as sources to match against, you can use this endpoint to upload your files.

If your project is already started, and you upload new source files, that is considered a new Batch, so creating a new Perfect Match Batch Mapping associated with your project is a must.

Can you please provide more details about your specific use-case? It will help us provide the correct assistance.

Thank you,

Rares.

RE: Potential outage at Dec 27th, 10:01–22:30 PST

Laszlo David — Tue, 20 Jan 2026 08:34:17 GMT

Evgenii Samarin Luca De Franceschi , please provide details, tenantId, projectId, start request timestamp, I need this details to be able to do a targeted investigation. Please see eu.cloud.trados.com/.../how-to-report-an-issue

RE: How to retrieve a project's current and future tasks

Henk Hendriks — Tue, 20 Jan 2026 08:11:30 GMT

Hi Laszlo,

Thanks! That does indeed work.

Best regards,

Henk

How to retrieve a project's current and future tasks

Henk Hendriks — Thu, 15 Jan 2026 13:49:42 GMT

Hi,
I'm using the API to create a connection between our internal TMS and Trados Team. One of the things I want to do is retrieve the translators and reviewers assigned to a project. I'm trying to do this with the List Project's Tasks endpoint. The information this endpoint provides only seems to include details of the current task.

So if the project's workflow has a translator and a reviewer assigned to the Translation and Linguistic Review stage respectively and the project is at the Translation stage, the details provided by the endpoint do include the assigned translator but not the assigned reviewer. Is there a way to retrieve both? I have tried to specify the field project.workflow.taskConfigurations but that information doesn't get included.

Regards,

Henk

RE: Potential outage at Dec 27th, 10:01–22:30 PST

Evgenii Samarin — Mon, 19 Jan 2026 11:39:25 GMT

Hello!

A bit of context here: the problem is that our client did start the translation workflow, but we haven't received the request on our side during the specified time period. Can you confirm that there was an Intento Translate step in the workflow queue that is not called via API?

RE: How to retrieve a project's current and future tasks

Laszlo David — Fri, 16 Jan 2026 10:06:45 GMT

please try the https://eu.cloud.trados.com/lc/api-docs/fd9ee0beb37ca-get-project with field projectPlan.taskConfigurations.

description states:

The configurations of the tasks that will be created in the future.

Available now directly after project creation, project does not need to be started to be populated.

This is enough to be retrieved once per project, (assuming the initial request of

[quote userid="3666" url="~/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60105/how-to-retrieve-a-project-s-current-and-future-tasks"]field project.workflow.taskConfigurations[/quote]

was on task level (this is redundant, and will do multiple unneccessary calls)

Clarification on API Status Messages for Canceled vs Error Files

Luciana Scocco — Wed, 17 Dec 2025 13:31:09 GMT

Hi team,

The developer team for our connected application (Translation Request Tool/TRT) have recommended I reach out in relation to this.

We’ve identified an issue related to the Trados API behavior: currently, the same generic “error” message is sent to TRT both when a file is genuinely in error (and potentially fixable) and when it has been canceled. Since the API does not provide a distinct “canceled” status, this is causing mismatched statuses and even target retrieval failures in TRT.
Would it be possible for the API logic to differentiate these two scenarios by sending separate messages for:
• Canceled files
• Files in error

This distinction would help us handle these cases more effectively.

Thank you for any insights you may provide at this point.

Best,