I had a look at the docs you linked for Google and it indeed seems overly complicated. I mean an endpoint that does send something to a payed service doesn't need OAuth in my opinion, it just needs a valid API key to associate the request with your account, there is no "identity element" involved to distinguish between various users, that's what OAuth is usually used for in my world... e.g. I'm not seeing the point in going trough all the OAuth hoops for something relatively simple like that...
but:
but of course I don't know if you intend to use the Advanced API (v3)? Otherwise you might be able to get around with a regular API key / Bearer token auth, here's how you'd do it: https://stackoverflow.com/a/70656679/4428236
If you don't want to bother at all with authentication you could try and get inspired by this https://github.com/Stichoza/google-translate-php/blob/master/src/GoogleTranslate.php , it basically "abuses" translate.google.com (the web version) to translate stuff for free 😉.
The person from my company already using google elsewhere said to use API V3. I didn't ask why. I'm not sure if there is a good reason, but I think we have decided to go our own way with the community and try something simpler (looking into Microsoft but I plan to take a look at Libretranslate too). Also, with Aurora on the horizon we haven't decided if we want to invest the effort in this yet, but I'd like to start playing with it on stage.
Thanks for all the help!
