Error 400: invalid_scope [https://www.googleapis.com/auth/keep.readonly, https://www.googleapis.com/auth/keep] [210500028]

WAI

Bug

Status Update

No update yet.

Description

la...@gmail.com

created issue #1

Dec 14, 2021 02:31PM

If we check the documentation for Notes.list method you will notice that it states that you need to use one of the following scopes

I have tested it with the following C# code

 var credential = await GoogleWebAuthorizationBroker.AuthorizeAsync(GoogleClientSecrets.FromFile(clientSecretJson).Secrets,
                new []{KeepService.ScopeConstants.KeepReadonly, KeepService.ScopeConstants.Keep},
                "userName",
                CancellationToken.None,
                new FileDataStore("credPath", true));
           
           
            var service = new KeepService(new BaseClientService.Initializer()
            {
                HttpClientInitializer = credential,
                ApplicationName = "Google Keep Oauth2 Authentication Sample"
            });

            var notes = await service.Notes.List().ExecuteAsync();

In both instances I get the following error message

Error 400: invalid_scope Some requested scopes cannot be shown: [https://www.googleapis.com/auth/keep.readonly, https://www.googleapis.com/auth/keep]

As you can see from the error message this the library is passing the proper scope as documented. Its the Google keep api itself that is refusing the scope.

Comments

la...@gmail.com <la...@gmail.com> #2Dec 14, 2021 02:40PM

Sorry i forgot to mention this was tested with a normal gmail account as well as a Workspace domain account.

se...@google.com <se...@google.com> Dec 15, 2021 08:20AM

Assigned to se...@google.com.

se...@google.com <se...@google.com> #3Dec 15, 2021 09:25AM

Hi,

Thank you for reporting this behavior.

I have been able to reproduce it and have forwarded it internally.

Regards.

lo...@google.com <lo...@google.com> #4Dec 22, 2021 09:35AM

Status: Won't Fix (Intended Behavior)

Hello, thanks for your patience.

In the current state, Keeps API can only be used through domain-wide delegation, with service accounts or an OAuth client ID, only for enterprise apps.

You can reach the resource following this path Admin Console> API Controls> Security> Domain-wide Delegation

If you have more doubts on how to use or configure Domain-Wide delegation, you can follow this guide.

Cheers!

[Deleted User] <[Deleted User]> #5Jan 12, 2022 07:52AM

Hi

For Google Keep API use, Can we need mandatory to purchase Enterprise account?

Thanks

Enterprise.PNG

12 KB

View

Download

[Deleted User] <[Deleted User]> #6Jan 13, 2022 04:18AM

Hi

Please provide any update on it.

Thanks

[Deleted User] <[Deleted User]> #7Jan 17, 2022 08:46AM

Hi

Please provide any update on it.

Thanks

gi...@gmail.com <gi...@gmail.com> #8Mar 21, 2022 06:22AM

Hello, Is there any update on this front on normal, gmail accounts?

ja...@gmail.com <ja...@gmail.com> #9Jul 3, 2022 04:09PM

Also interested. This appears to make Google Keep API unusable for average engineer. This thread seems to suggest that we've coupled access with Google Workspace accounts - specifically enterprise class only. Is that true?

If it is true, then maybe just re-brand the API. It's not Google Keep API if you can only access through another product. This sounds like a Google Workspaces API. It's usable only by Workspace customers that has the neat feature of access Keep-like content.

wo...@gmail.com <wo...@gmail.com> #10Aug 29, 2022 03:33PM

Any update on this for regular gmail accounts?

og...@gmail.com <og...@gmail.com> #11Sep 5, 2022 08:57AM

I would like to see this available for regular user accounts too - it's a great service and it's unclear why this API cannot be accessed by regular Google accounts

dr...@gmail.com <dr...@gmail.com> #12Mar 16, 2023 09:31PM

The status of this is listed as "Won't Fix (Intended behavior)", but how can the intended behavior be to lock Keep API away from the average google user? Its a product in the free google space that can be used without a Workspace account, and definitely without an Enterprise app, so why would the API be locked behind Enterprise?

Can we get an re-evaluation on how this would be considered intended? Feel like I should be able to at least readonly my own Keep Notes from an API for better accessibility.

as...@gmail.com <as...@gmail.com> #13Apr 11, 2023 11:55AM

I like poke on this thread and like to check if keep api's can be available for regular user accounts. Currently documentation related to keep API doesn;t mention as its intended to be available only behind enterprise. Its very wague and response on thi thread from google as "Won't fix (Intended behavior)" is also not clear and doesn;t give what to expect in coming days.

Appreciate a clearer response and path forward on this thread from Google for availablity of keep api for regular users.

br...@gmail.com <br...@gmail.com> #14Apr 11, 2023 07:56PM

If they fix this, then they'll be opening up all kinds of to-do apps to sync lists with notes through APIs. You'd think this would be in Google's best interest, but apparently it isn't.

bc...@gmail.com <bc...@gmail.com> #15Jul 9, 2023 02:12AM

This bug shouldn't be "Won't fix (intended behavior)". It's not working for Enterprise users (using Google Workspace) without Super Admin permission.

Message last modified on Jul 9, 2023 02:15AM

ad...@gmail.com <ad...@gmail.com> #16Jul 17, 2023 04:09PM

Hi,

Just to ensure I understand this correctly this is only meant to work for Enterprise Google Workspace accounts.

So this is not meant to work on normal Business Google Workspace accounts, if so I'm not sure why that should be the case given it's relatively basic functionality.

With the use of apps like Akiflow to connect API's Google runs the risk of losing users of Keep if it makes the API's unavailable to their users.

Thanks

ba...@gmail.com <ba...@gmail.com> #17Sep 12, 2023 05:16PM

Any updates for regular Gmail accounts?

ch...@rtbrick.com <ch...@rtbrick.com> #18Oct 29, 2023 09:15PM

I have the same problem.
I need a way to create notes via api call.
Any updates?

co...@gmail.com <co...@gmail.com> #19Oct 31, 2023 02:25PM

It's been years since this was first reported and Google is visibly not interested in providing the api to non-enterprise users, which is very frustrating.
My opinion is in a year or so we will see Google Keep in

https://killedbygoogle.com/ , since people will stop using the application because of limitation of not being able to integrate with any other applications.
I wanted to make an integration with Home Assistant, so users could see their Keep lists directly in home assistant, but I guess the solution is finding something else instead and move as further away from google as possible.

Only some of the "integration" projects I been looking into last days that are affected by current changes that are unable to fetch information from Google Keep anymore:

https://github.com/PiotrMachowski/Home-Assistant-custom-components-Google-Keep

https://github.com/fcastilloec/gkeep-list-sync

https://github.com/djsudduth/keep-it-markdown

https://github.com/kiwiz/gkeepapi

It's truly a shame, but there are better alternatives out there anyway.

ur...@gmail.com <ur...@gmail.com> #20Feb 6, 2024 10:37AM

Why do Google remain silent here?
Could anyone find a working method to connect to the Google Keep API?

ha...@gmail.com <ha...@gmail.com> #21Apr 16, 2024 02:55PM

Very disappointing to see this.
This personally forces me to transition to something like Microsoft Todo, since I can't integrate Keep into my own applications.
It also means I will have to completely trash my idea for a nice PowerToys Run plugin for Keep.

mm...@mafro.net <mm...@mafro.net> #22Aug 22, 2024 05:21AM

I use the official API on my Google Workspace account, using a GCP service account to authenticate and domain-wide delegation set up.

I'm very surprised this is only because I'm an "enterprise" customer! (There's only 2 users on my Workspace account)

Message last modified on Aug 22, 2024 05:22AM

cd...@puehringer.at <cd...@puehringer.at> #23Oct 16, 2024 09:34AM

I think this error only occurs with the following conditions:
- additional scopes like gmail, drive, ... (it works only with

https://www.googleapis.com/auth/keep;

https://www.googleapis.com/auth/keep.readonly;

https://www.googleapis.com/auth/userinfo.email)
- OAuth 2.0 Desktop Clients (WEB-Clients are fine)

With Postman an the following scopes (