While hitting google api with secure key and token, I am getting score as 0.0 and isSuccess is coming as false. But, on Google Recaptcha Admin console, I do not see any suspicious request. The question here is if the score is 0.0 then it should come on admin console and highlighted as suspicious request but it is not. Please help me understand what am I missing? I would like to understand on what basis google calculates the score.
Related
I've implemented recaptcha v3 per the docs, but in our contact form when I do the callback to get the token and parse it in the backend, I'm getting a score of 0.9... all the time. Well ONE came back at 0.7, but we're getting considerable amounts of bot spam which shouldn't be at 0.9 one would think. We went to v3 because v2 was giving just as much spam.
If you have normal scores, can you answer a couple quick questions?
You loading it on every page (in the template), or just your contact form
What (if anything) are you using actions for, the docs just kinda show "submit" and I'm not sure what else to issue a challenge for that isn't a "submit"...
Is there something I'm missing?
To test a low score you can simulate a browser with custom user-agent, for example "Googlebot/2.1"
Screenshot from my chrome dev tools
Not able to differentiate between price per request and price per session in Google API
I'm facing difficulty in
understanding some billing related terms for Google API. I know, this question might be more suited for support directly from Google. I tried but not getting satiesfactory response.
I was going through this URL:
https://developers.google.com/maps/billing/understanding-cost-of-use#ac-per-character
Here both 'price per request' and 'price per session' has been provided.
While I understand the difference between request and session, my question
is related to example provided in the same link, which is like this :
Places Autocomplete Request (input=”paris”, session_token: XYZ)
What I know, in google API, we just pass an API KEY to get results, but above seem to have required session_token. This has confused me. How can I pass session_token, when google has provided just an API KEY to me after creating billing account?
Is API key same as Session_token or does that mean, I need to get session token after 'first' passing API_KEY via code.
I'm not able to find good example explaining this till now.
Thanks for your help !!
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.
I wonder if someone else has experienced the same issue, and might have an answer to it.
I am using the Google Places API. There I do two kinds of requests
https://maps.googleapis.com/maps/api/place/textsearch/
and
https://maps.googleapis.com/maps/api/place/details/
After I have done about 20,000 of these requests my Quota of 150,000 has been eaten up, and I do get an error message.
The strange thing is, when I look at the Google API Console I can see the following:
In the API & Services Section I can see the following (which reflects the real requests I have done)
and in the IAM & admin section I do see a much higher value
This looks artifically high, and is limiting the service way to early.
Does anyone else have the same issue?
I figuert out, why there is this difference in request in the API view and requests in the Quota view.
When using the TextSeach Places API, each text search request, will be multiplied by a factor 10 towards your free contingent.
it is mentioned at this page:
TextSearchRequests
In my application I have been calling google prediction API continuously for an array(size: 4000 aprox) of strings. I observed that after some api calls it starts giving response as Undefined, it continues for some time and then gives result fine. This is happening frequently.
I have checked their api documentation, but couldn't find any rate limit or any such restriction. Also there was no error logged in Google API manager dashboard.
Does anyone have any idea why its happening like that.