Guillaume Goemanne 

We are internally going through the exercise of setting up a new Google Project up and also putting in place custom translations / glossaries.
We are finding it challenging and the fact that you got as far as a JSON file is remarkable.

Just a worthy note.
When it comes to supporting custom models in Google that then integrate into Studio -  is limited.
Within Trados Studio, we support AutoML and not the later Google Cloud API.
This is something we are trying to fix. I dont have a date, as to when we will get this implemented. But its something we are looking into hence we are resetting all our accounts as mentioned above.
However if you are using Language Cloud then we support both.

However non of that addresses your language question so let me try see whats happening.

JSON files typically support the custom model aspect including glossaries.
The fact you have not made it that far suggests the JSON file you are referencing may not be the right authentication protocol for you.

If I understood you correctly and you have nothing custom setup, implies you are simply trying to use "vanilla/standard" Google MT.
In this case please can you try use the API Key which is linked to your Google Project: https://console.cloud.google.com/apis/credentials 

Looking forward to your followup

Lyds

Dear  Lydia Simplicio ,

Lydia Simplicio said:

We are internally going through the exercise of setting up a new Google Project up and also putting in place custom translations / glossaries.
We are finding it challenging and the fact that you got as far as a JSON file is remarkable.

Thank you for your reply. It's a huge relief to see I'm not the only one. I generally consider myself moderately tech-savvy, but this Google Cloud Console makes me question that assumption, a lot.

The RWS API documentation gives general directions as how to add the API to the resources in Studio, but as to the exact steps and settings to follow in the Cloud Console, there doesn't seem to be very clear instructions anywhere if you want to use the Advanced V3 option. Setting up the Basic V2 was easy enough as soon as I had the API key, thanks to a YouTube video I found (Link). 

Lydia Simplicio said:

When it comes to supporting custom models in Google that then integrate into Studio -  is limited.
Within Trados Studio, we support AutoML and not the later Google Cloud API.

I'm afraid I don't understand the difference (yet). Are you saying it is currently impossible to use custom models and glossaries for different clients with the current Trados plugin? It seemed the documentation said otherwise. Or is there more than one way in the Cloud Console to do this and Trados only supports the older version of both? The only APIs I'm currently trying to use are the Google Cloud Translation API and AutoML.

Lydia Simplicio said:

However non of that addresses your language question so let me try see whats happening.

JSON files typically support the custom model aspect including glossaries.
The fact you have not made it that far suggests the JSON file you are referencing may not be the right authentication protocol for you.

As for the error I wrote about a few days back, it has been replaced twice already by other errors, and once I somehow solved them, I landed back on this one. But never did it just add the resource to Trados. If you could tell me what the right protocols would be and where I need to set them up, I'd be delighted.

Somehow it feels like I'm taking steps back instead of forward, while still going around it in circled... If I could find a detailed guide I wouldn't mind starting a new project from scratch.

Lydia Simplicio said:

If I understood you correctly and you have nothing custom setup, implies you are simply trying to use "vanilla/standard" Google MT.
In this case please can you try use the API Key which is linked to your Google Project: https://console.cloud.google.com/apis/credentials 

I did add a custom model it doesn't recognize (cf. above), but was unable to understand how to create custom glossaries (the "navigate to glossaries" option in the Trados plugin brings me to a "bucket" page I haven't come to yet). The API key you mentioned worked for the Basic V2 option of the Trados plugin (cf. above).