You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now for authorization \w server-side flow OAuth 2.0 from Google we are tell user to create new Quickstart project in his API console (under his own account).
It does have only a limited number of API requests and some permissions/scopes are severely capped (only 100 -modify calls) e.g those used to mark email as read.
May be a better idea could be to have a documented option of using pre-registered, verified app so that the user can skip API console configuration steps and avoid the hassle of app verification (can take days :/)
The text was updated successfully, but these errors were encountered:
bzz
changed the title
Switch to a new application in API Console instead of Quickstart
Switch to a new app in API Console instead of Quickstart
Nov 27, 2019
bzz
changed the title
Switch to a new app in API Console instead of Quickstart
Provide a choice: new "Quickstart" project in API Console or an existing pre-authorized app
Nov 28, 2019
bzz
changed the title
Provide a choice: new "Quickstart" project in API Console or an existing pre-authorized app
choice: create new "Quickstart" project in G Console or use existing pre-authorized app
Dec 11, 2019
Right now for authorization \w server-side flow OAuth 2.0 from Google we are tell user to create new Quickstart project in his API console (under his own account).
It does have only a limited number of API requests and some permissions/scopes are severely capped (only 100
-modify
calls) e.g those used to mark email as read.May be a better idea could be to have a documented option of using pre-registered, verified app so that the user can skip API console configuration steps and avoid the hassle of app verification (can take days :/)
The text was updated successfully, but these errors were encountered: