Management of source document versions

We’re now starting another phase of our integration and I have a question regarding this important aspect:

  1. Management of source document versions
    We’d like to clarify the best approach for managing source document versions via the public API.

Use case:
As a requester, I upload a new version of a source document through the our own client portal. This new version should be properly added in Trados Cloud.

We reviewed the public API endpoint /tasks/{taskId}/source-files/{sourceFileId}/versions, but it requires a taskId, which doesn’t suit our case.
Do you have any alternative method or recommended entry point in the API to handle this use case?

Parents Reply
  • Hi  

    Jean-François asked me to follow up with some additional context regarding our use case.

    Assuming that source documents have already been uploaded to Trados Cloud, we often need to update these documents—either to fix content errors or to add/remove sections. This update can happen at any point in the project lifecycle, sometimes during preparation before any tasks or assignments exist, or later during the active translation phase.

    The main issue we’re facing is that the endpoint available for adding a source file version — https://eu.cloud.trados.com/lc/api-docs/93b284fd6ee08-add-source-file-version — requires a taskId. Unfortunately, in our scenario, we often need to perform these updates before any task has been created or assigned to the document, which makes this endpoint unusable for us.

    We’d like to know if there is a way to update a source document (i.e., add a new version of it) without requiring it to be associated with a task. That would allow us to support updates during early preparation phases, and task assignments could then follow at a later stage.

    Looking forward to your insights on whether this is feasible via the current API or if there might be an alternative path.

Children