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 Children
No Data