gapi | Google API command-line client , written in Go | REST library

The Google apis php client library is a library designed to use Oauth2 to access google apis. It uses the PHP scripting language

The Google Sign-In JavaScript library is a JavaScript library used for Signing in users to your application using their google account.

First off Oauth2 is not sign in. Second Php scripting language is not the JavaScript scripting language.

These are two different things. The php client library has nothing to do with gapi which is part of the JavaScript client library.

I would check the rest of your system to ensure that you are not using the JavaScript library. Your php library is unaffected.

Documentation regarding Google Identity Services JavaScript SDK just became available.

In contrast with Sign In With Google, which only handles authentication (see Authentication and authorization), this library handles OAuth tokens (see Using the token model) to access Google APIs, and so can be used as a complete replacement to gapi.

Please notice though that GIS doesn't handle calling the API, and so Google suggests to keep using gapi.client for that (ref):

You can safely continue using the gapi.client module from the Google API Client Library for JavaScript, and take advantage of its automatic creation of callable JS methods from a discovery document, batching multiple API calls, and CORS management functionality.

So, after getting the access token via GIS, you can either use gapi to call the API, or call the API without any of these libraries (in the example below and in the official docs, XMLHttpRequest is used for that).

In the new Gooogle Identity Services, the authentication moment and the authorization moment are separated. This means, GIS provides different APIs for websites to call on these two different moments. You cannot combine them together in one API call (and UX flow) any more.

In the authenction moment, users just sign in or sign up into your website (by leveraging the information shared by Google). The only decision users need to make is whether they want to sign in (or sign-up). No authorization-related decison need to make at this point.

In the authentication moment, users will see consistent One Tap or button UX across all websites (since the same scopes are requested implicitly). Consistence leads to more smoothly UX, which may further lead to more usage. With the consitent and optimized authentication UX (across all websites), users will have a better experience with federated sign-in.

After users sign-in, when you really want to load some data from a Google data service, you can call GIS authorization API to trigger an UX flow to allow end users to grant the permission. That's the authorization moment.

Currently (August 2021), only authentication API has been published. If your website only cares about authentication, you can migrate to GIS now. If you also need the authorization API, you have to wait for further notice.

It seems that the arguments of DoubleClickCampaigns.CampaignCreativeAssociations.insert() are as follows.

It is not possible, it needs the 'courseId' parameter to return the data. A workaround would be listing all the courses with 'Method: courses.list' [1], get the Id's for all courses and create a cycle so it gets the course work for all courses.

[1] https://developers.google.com/classroom/reference/rest/v1/courses/list

I thought that in your script, https://docs.googleapis.com/$discovery/rest?version=v1 of gapi.client.load("https://docs.googleapis.com/$discovery/rest?version=v1") is used for Google Docs API v1. I think that the reason for your error message of Uncaught TypeError: Cannot read properties of undefined (reading 'files') is due to this.

In your goal, it seems that you want to create a folder into a specific folder. In this case, please use Drive API. But, when I saw your current script for creating the folder, Drive API v2 is used. So, please modify as follows.

I believe your goal is as follows.

• You want to create a new Google Document using Google Docs API with Javascript.
• You have already been able to use Google Docs API.

In this case, how about the following modification?

First, please modify your scope from https://www.googleapis.com/auth/documents.readonly to https://www.googleapis.com/auth/documents.

And, please modify your script as follows.

Instead of using firebase I used a npm package called react-google-login, which provides the access_token. I used that access token to authorize the YouTube API, which worked.

https://www.npmjs.com/package/react-google-login

you can use html_to_json