REST API for Update Main Translation Memory Batch Task

Hello,

Our firm uses GS 2020 SR1 CU08 with Trados Studio 2022 17.0.6.14902, and I am trying to automate the finalisation process via Groupshare REST APIs.

So far I've found an API called "ProjectFinalize" and it works perfectly except that it converts the bilingual file into the native source file extension (e.g. Word document). I am seeking an API, or any workaround, just to have the Server-based TMs updated without finalising the file. Please find the screenshots below for illustration:

(Note: I am aware that the API interacts directly with GS instead of Studio, but I've attached the task sequences for purpose of demonstrating our goal, and that is, to just have the main TMs updated without generating any native files)

Screenshot of the ProjectFinalize API documentation showing the POST request format and example with placeholder HOST and projectId, and a sample authorization token.

Screenshot of the Batch Tasks interface in a software application with the 'Finalize' task sequence selected, detailing the tasks 'Update Main Translation Memories' and 'Generate Target Translations'.

Screenshot of the Batch Tasks interface with the 'Update Main Translation Memories' task sequence selected, describing the task to update the main translation memories with translated bilingual files.



Generated Image Alt-Text
[edited by: RWS Community AI at 4:06 AM (GMT 0) on 15 Nov 2024]
emoji
Parents
  • Hi ,

    Sadly, GroupShare does not have the batch tasks exposed at that level of granularity via the Rest API. 

    If you don't want to have the file finalized, but still update the translation memory you could use the file download Rest API call (HTTP GET /api/projectserver/v2/projects/{projectId}/download/{type}). 
    You need to pass in the query string the following parameters: 

    • languageFileIds
    • nativeFiles=true (this must be set to true so that "updateTms" parameter is taken into account)
    • updateTms


    The boolean parameter called "updateTms" will trigger the updating of server-based TMs. Calling the download endpoint will return you an archive with the native file - but the file will not be finalized.

    This might be your best option to achieve what you're after. 

    Cheers,
    Zoltan

    emoji
  • Thank you Zoltan!

    I've checked the API documentation and apparently the queries you've mentioned refer to an HTTP call without "{type}". Nonetheless, I've tried both as per the documentation, and unfortunately none of them works. The one proposed above with the correct endpoint (without {type}) gives a 500. As for the endpoint with {type}. It gives a 200; however, I've checked the server-TM, and there's no updates.

    emoji
  • The same HTTP calls are used by the GroupShare web application when you're downloading the target version of selected files. 

    It should be a HTTP GET to api/projectserver/v2/projects/{projectId}/download?languageFileIds={languageFileId}&nativeFiles=true&updateTms=true

    Could you check once again and if you don't succeed post the HTTP request, please. 

    emoji
Reply Children