Google Keep API - cannot add scope - google-cloud-platform

I am trying connecting to Google Keep API but i cannot add scopes in Google Cloud Console.
I have enabled Google Keep API in Library but still can't add scopes to access this API. I am getting this error:
The following scope(s) were not added because they are invalid. Please
update or remove these scopes: https://www.googleapis.com/auth/keep
https://www.googleapis.com/auth/keep.readonly
screen

I am running into the same issue. Upon further digging I found this explanation:
This API is an enterprise-only API used to create and manage the Keep notes within your domain, ...
Which was found in the Google Keep API documentation.
(Thanks to amanda-tarafa on 2021-09-03 found here.)

Related

Google Search Console API suggests enabling API for unfamiliar project number

I have an account that is the verified owner for a property listed in the Google Search Console. I'm working to set up API access to it. I have a principal created that has access to each of the Google Cloud projects that I intend to query the data from. I've enabled the Google Search Console API for each of these projects.
After I authenticate the principal via OAuth2 and use the access token (including the 'https://www.googleapis.com/auth/webmasters.readonly' scope) to make a POST request to the query endpoint, I get an error message back that reads in part:
Google Search Console API has not been used in project 256595xxxxxx before or it is disabled
I searched this number in my Google Cloud Console and manually clicked through each of my properties and it doesn't match any of the projects on my account. How do I identify which project this number is referring to and/or how do I change it to point to one of my own Google Cloud properties so I might access its API?
Note: This answer speaks to what it is I'm trying to do (but with Google Search Console API), except that the error doesn't reflect my project ID, so I'm stumped about how to move forward with enabling the API on it.
This didn't take long to solve. After listing all the projects in the Google Cloud CLI per the first half of the instruction here, I was able to identify the project as that which is used as the service principal to do the authentication in the first place (and not actually an account I intend to export any of the data to).

Google Sheet asking for authorization gets 401: deleted_client

I cannot seem to get past the Google Authorization pop that always returns Error 401: deleted_client.
I created a Google sheet script a while back and I need to get it working again. I made a GCP account and tried messing around with that for hosting the app but I realized I didn't need that so I deleted all of my projects and my billing account. But I still can't get past the Google Sheet error when it tries to authorize my account. This worked before I started anything with GCP and was fine.
I've seen other issues saying that there needs to have some fixes in the GCP account and that's fine and all but I do not want this connected to GCP at all. I will never use GCP again and I can't even find a way to shut down the account entirely without removing my Google account.
I've tried clearing all cache and cookies from chrome since the beginning of time like some others have suggested that doesn't fix the issue either.
Thanks in advance!
It's confusing but, if your script uses Google APIs you must associate the script with a Google Cloud Platform (GCP) project.
See Google Cloud Platform projects for an explanation of this relationship.
GCP projects are used to group enabled Google services, to provide identities and configure OAuth.
Please read the document but see (re)creating OAuth credentials.
You'll need to:
Create a GCP project
Enable Google services
Configure OAuth consent
DazWilkin lead me in the right direction!
The last thing that was needed was to go to the existing Google Sheet script, hit the gear in the left panel of the new editor, then change the GCP project number to match the GCP project I created with OAuth creds. Thanks again!

YouTube Player API with Exposed GCP API keys

Recently I received this Alert in the Google Play Console
Your app contains exposed Google Cloud Platform (GCP) API keys
I am using the YouTubeApi Player, and I believe the only why you can initialize it is using this line of code
youTubePlayer.initialize(DEVELOPER_KEY, this);
So beside added restrictions to my API key, is there any other way to remove the API Key from the code?
I tried using the GCP service accounts as suggested by Google, but I do not see how I can still use the YouTube Player without the initialize line of code.
I have same problem, and fixed this by using string R.string.google_api_key generated by google_services.json
change your code to:
youTubePlayer.initialize(getString(R.string.google_api_key), this);
how to get google_services.json:
create firebase project https://firebase.google.com/docs/android/setup?hl=id
get your google_services.json https://support.google.com/firebase/answer/7015592?hl=id
There are some tips on how to secure your API keys at Using API Keys documentation.
It is stated that embedding API keys directly in the code should be avoided, which is the way you are having it right now, therefore you are getting the warning message.
Follow the tips on that page and you should properly secure your API key. As soon as you do so, the warning will go away.
UPDATE
To avoid having a long discussion in comments, allow me to elaborate further providing this update.
Google provides different ways of authentications to give you more options for securing your apps based on your needs. The warnings are helpful tips to make your apps more secure when going in production or exposing to public. So in your case, it would be better to use a different way of authentication.
API keys can be used in server side. e.g. If you are using an API key to authenticate a 3rd party service from an App Engine app, you can use this key as you already have it, since it is impossible for the key to get exposed. (Avoid using API keys in JavaScript since inspecting the page in the browser will expose the API key as well)
In your case, since you are developing an Android app and/or an iOS app, having the API key in the code is dangerous. Because, anyone can use the .apk or the .ipa file and find a way to access it. Therefore, for developing Android apps and iOS apps it is suggested going with different authentication method. The other authentication method supported in YouTube player API is using OAuth 2.0. For more information you can check the Registering your application documentation.

Issues Enabling Google Ads API on Google Cloud Platform Console

Every time I try to enable Google Ads API on the google cloud platform i receive the following error:
API solution not found with service name: googleads.googleapis.com
I've set up an ads manager account under the same email and generated an API access token. I've tried setting it up under different emails and in different browsers and I have even tried using incognito mode to see if that would resolve the issue per the instructions of other threads. I've also created the oauth2 credentials for the project I'm trying to give access to the Google Ads api.
I really just need to enable the Google Ads API. Any help would be much appreciated.
For me just disabling ad-blocker fixed the issue.
After paying for Google support, this is what i found:
Disable all Google Chrome extensions
Start Google Chrome in Incognito Mode
Sign into Google Cloud Console and add the api from the api library.
It's that simple.

How to get Authorization token for Google Cloud Storage

I am trying to integrate Google cloud storage API for transferring all my web app uploads to google cloud storage.
According to documentation, I need to pass Authorization header every time making a new request but am not getting where I can get that Authorization token? I tried so hard I checked a lot of Git repos and StackOverflow discussions.
Still am not able to find answers.
For more information:
You can get the Authorization token in OAuth 2.0 Playground. Follow the steps described. Notice that in step 2 you have to click on “Exchange authorization code for tokens” to obtain the “Access token” you need. I suggest you to follow this Uploading objects guide (REST APIs) the first time you try it.
Perhaps you can do this using the Cloud Storage Client Libraries.