Google API Calendar PHP SSL error - caching

I have written a code for fetching Google Calendar events using Google Api Package Php. It works perfectly fine. Just that, once it fetches details of an user. It is caching the details in the server. I am using Centos server. To my knowledge, it has something to do with Google api caching. Because of that I have to wait for 15 mins before another user's details can be fetched else it will show the previous user details.

Related

Review Data - Google My Business/Business Profile Performance API: Permi

I need to use the GMB API to get review data but I get the following error.
Google My Business API has not been used in project 341557982028 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/mybusiness.googleapis.com/overview?project=341557982028 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.
When I click on the link I get "failed to load" (see image attached). I enabled all the APIs (8 or 9) but still doesn't work. I completed the form and got the authorization from Google from the app already. Location data is working fine.
I really need help with this one!

My Google API keeps returning a limit reached error, when I am sure I am under the limit

I am currently building a NodeJS backend app that is querying the Google Calendar API. I have setup a new project on Google Cloud API platform and have generated all the required credentials. As stated by the google calendar API page, the allowed queries per day is 1,000,000. Since I am only querying for testing purposes at the moment, I am sure that I haven't even hit a 100. Yet whenever I try to query the API it returns the error:
"The API returned an error: Error: Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup."
Also I have noticed that the dev console has generated a API key for me. Where am I supposed to put that?
My initial thinking is that Google API requires me to perform an additional signup using some CLI tools or something along those lines to signup. If not, where am I supposed to sign up?
Thanks in advance.
Note: I already have all the information from the cloud platform such as client_id, client_secret, project_id.
In "Error: Daily Limit for Unauthenticated Use Exceeded", they key word is Unauthenticated. Your request to the Calendar API is missing an OAuth Access Token. You will need to research Google OAuth.
This question has been answered many times. Please learn how to search SO for similar questions whenever you post a new question. https://stackoverflow.com/search?q=google+oauth+%22daily+limit+for+unauthenticated%22
To anyone who comes across this post in the future. I fixed the issue by using the project generated by Google Calendar API site (https://developers.google.com/calendar/quickstart/nodejs) by clicked the big blue "Enable the google calendar api" and then changing the name of the quickstart project that was generated. I don't know why it works now but it does and it's been working quite stably so far. Lets see how to goes.

How to access user Google Fit data from backend

I write backend ASP .NET Core API and I need to read user Google Fit data.
I created an Android app that gets the server auth code and sends it to backend. As far as I understand, I need to get user token and then use it to access Google Fit. I tried to find libraries for it and failed. I also tried to get user token using Postman and got the following error:
{
"error": "invalid_grant",
"error_description": "Bad Request"
}
Am I doing something wrong?
You may refer with this thread: Using google fit api from a backend server.
To access from a back end server you will need to use the Rest API's There is documentation at developers.google.com/fit. You should be aware that the Google servers and the Android device are synced irregularly so data on the device may not be visible for hours or even days.
You may also check this link on how to read user's Google Fit data via REST API.
There is a mechanism for Android apps to obtain offline access for web back-ends highlighted in the CrossClientAuth guide from your question. With offline access, you can theoretically serve or store that data in any way that the user has consented to. Any access controls of that data to another person is something that you'd have to handle on your own.

Working with Googles API's in front end or backend?

I just started to work with Google API's (Calendar and Gmail for now). I already got both examples working on both my Frontend (React) and my Backend (Java - Spring).
I have the following doubt, If I want to enable users to be able to send email's using the oficial API not javax.mail should that be done on the Backend or it can be done on Frontend? Since the official documentation only shows examples on Java and Python.
If the answer is on Backend how will users be able to authenticate via OAuth2 If they are "not supposed" to see server-side information.
Thanks
Ok for does looking for an answer. I found the following guide...
https://developers.google.com/identity/sign-in/web/server-side-flow#step_1_create_a_client_id_and_client_secret
Basically you can get a client-side one time access code which is send to server-side where it can get a long-live access_token in order to have offline access once correct authentication has happened.

Why is the Google Apps Marketplace UpgradeableApp API returning this response on a successful upgrade?

I'm in the process of writing a script to upgrade an old OAuth 1 listing to a newer OAuth 2 listing in the Google Apps Marketplace. I've successfully linked the old listing to the new one and upgrading it via my script is possible. However, the response I'm getting on a success case is...strange.
According to the documentation, the response should have an upgrade_status field, with either SUCCESS or various failure statuses. Instead, the response.body looks like this on a success:
{"kind":"appsmarket#upgradableApp"}
When I have the user check out their Google Apps admin panel, everything seems to have worked. The discrepancy between the docs and the actual response is a bit concerning though. Why is this happening?

Resources