google-api-python-client VS google-api-javascript-client

We uploaded one of Google’s sample Python scripts to Docuwriter to test some of the code documentation types, starting with General Documentation:

Google has documentation and 'getting started' resources for the GMail API, but the sample script implemented in their 'Python Quickstart' guide is using syntax that is documented separately in the Google API Python Client docs and GMail API docs.

First hit on google: https://github.com/googleapis/google-api-python-client/issues/1640

I'd recommend using one of the clients vs trying to assemble the requests yourself. The Python client is a good place to start.

The main functionality is handled by the Thermostat class. On creation it creates a service object using the Google Python API Client. That's used later to help build and execute API requests. At app exit the service object is closed.

At first, to simplify the procedure, I started with the credentials of an open source email client. I then used the tool mutt_oauth2.py (which is a streamlined version of google-api-python-client).

Based on my understanding, this is now only possible via through OAUTH2. After several failed attempts, it seems I found the official supported library, that is google-api-python-client.

API client for Python

Documentation. I've encountered several non documented requirements on various services that are just frustrating for no reason, until you find the correct answer on StackOverflow or GitHub. This can be a known issue that is unfixed for years, even though it's only a change in documentation. Again, Google's support teams keep claiming to file "internal bug reports" that go nowhere for years. Google is so busy always developing the "next big thing" that they forget to invest in their own existing tools that developers count on. See this example Issue from 2015 that was still gaining comments in 2021!

Sometimes different JavaScript libraries are needed for in-browser vs node.js. I think that the npm googleapis package is specifically for node.js, and for in-browser use you need to use https://github.com/google/google-api-javascript-client

Incorrect, twice. We're not asking you to trust us, you can verify it yourself, Google Auth's scripts are open source. Here and here. They're also available in our repo as well.

API client for JavaScript

One interesting consequence of this is that Google's own javascript api client will no longer work with MV3 and there are apparently no plans to ever make it work.

See https://github.com/google/google-api-javascript-client/issue...

So effectively this means extensions on MV3 can't easily access Google apis, which is quite unfortunate since Chrome extensions in particular made Google authentication super straightforward (piggybacking off of chrome's built-in google authentication). If someone knows a better way I'd love to hear it.

I believe the reason that the current incarnation of the javascript library won't work is because it modifies the dom to add script tags to fetch and run the api library (or components of it), which is specifically what MV3 will disallow AFAIK.

What I want to do is contact the developers of this library. I looked at the google-api-client-libary for Javascript and thought about raising an issue due to the insufficient documentation, but the owners seem to be very slow in responding. How do I contact the developers and perhaps get a response in 1-2 days or at most a week?

Have you read the documentation and source? If so, maybe include the part that is confusing to you so people can help explain that specifically.

Here is an example of using Google APIs Client Library for browser JavaScript, aka gapi with no authentification. The Google Api we are calling here is Calendar API.

I have a Vue 3 / Quasar / TypeScript app that is using the Google API Client Library for JavaScript (also known as gapi).

I know that this is problem with server side rendering in my Next.js app and people recommend using a client side package like this https://github.com/google/google-api-javascript-client. But google-api-javascript-client doesn't have any documentation on authenticating with a .json credentials file instead of an API KEY which I do not have.

I've authenticated the user using Firebase successfully, giving me a user object to play with, however, to ping the Calendar API, I'm using the gapi library. This means, though, that I have to do the whole OAuth2 cycle twice - once to 'log in' the user to the application, and once to 'authorise' the application to use the user's token to use the Calendar API.