I had an application using the Google Vision API running fine for nearly a year. It wasn't running for a few months and when I ran it recently, it always returned 400 errors. I went to the account settings and noticed my key was gone. I entered a new one and updated my program. However, it still always gets a 400 error. It does so no matter what key I use (valid or not).
I looks like it isn't accepting the key.
Any idea what the issue might be?
Any way to test that a key is valid?
Related
When calling https://graph.microsoft.com/v1.0/teams/{id}/channels/{id}/messages/delta endpoint, I am getting a `400 (Bad Request) response.
I am experiencing the same issue in Microsoft Graph Explorer even after providing Admin Consent.
Below are some relevant posts I found where people are experiencing similar issues
https://github.com/microsoftgraph/microsoft-graph-docs/issues/7631
https://learn.microsoft.com/en-us/answers/questions/201576/when-i-call-the-api-to-get-message-list-by-using-d.html
MS Graph - Conversation delta API not working for some channels
However the beta version of the aforementioned endpoint is functioning properly, but the beta version of Graph API is not advisable to be used in a production app.
I just did a test on your problem, and I found that indeed as you said, when the beta version is used, the api call is successful, and when the v1.0 version is used, it reports a 400 error. This is strange because the documentation does not Too much explanation on this. So, I think this is an unknown error, you can report your problem to Microsoft.
I'm having an issue with an Analytics API batch request that I am doing, it was working and now it isn't without me changing anything. I know Google are making changes to their batch endpoints and I believe this is what is causing my errors.
https://developers.googleblog.com/2018/03/discontinuing-support-for-json-rpc-and.html
I am using the .NET client library with the AnalyticsService. Having read through the link above I'm fairly certain I've done what is needed for my batching to continue to work.
Here is a screenshot of the .NET instructions
I've upgraded all Google libraries to the latest versions, I've checked the AnalyticsService object and can confirm the BatchURI is no longer the Global HTTP Batch endpoint www.googleapis.com/batch, it is showing as https://www.googleapis.com/batch/analytics/v3, but I am still getting 400 Bad Requests. Is there something else that I am missing, or do I have to wait until the 12th of August when Google say the switch will be complete?
Thanks
Update: I created an issue on GitHub, apparently it is an internal issue, currently waiting for a fix, see here to keep updated:
GitHub Issue on .NET client library
We are not able to call any of our APIs on our organization, we are receiving classification_failure on each API call even the testing ones that are related to weather.yahoo.com etc..
each time we open the API proxy the message the following message is displayed (No server entry found with ID 1c53328c-57b6-4f69-bdf0-ce4b39e64ef3) .
we had an increase of the traffic on our apis , is it possilble that apiggee closed the api because they monitored high volume of traffic.
I created another organization it is all working fine
I passed this along to our support team. It may be a hardware problem. (Just saw this problem with a colleague and he got it resolved. Check yours to see if it was related)
You can also email help#apigee.com with details about your org and traffic spike.
I've enabled the Google Maps v3 (and v2) services in the API console and then generated a browser key.
I just swapped a maps.google.com/geo?q= URL for the below URL (example):
http://maps.googleapis.com/maps/api/geocode/json?sensor=false&key=newbrowserkeyfromconsole&address=ALE+BILSERVICE,ALVANGEN,Sweden
It is called with 1600 HTTPGET requests in one run, but now it doesn't even work when pasting 1 URL in a browser!
EDIT: I wrote that it runs once per day, but that is false. Fixed street addresses don't suddenly switch GPS coordinates. ;)
I looked at several similar threads, where generating a new browser key in the API console seemed to work. But not for me. I'm running this from "whatever client ip", so I left the url filter box empty when generating it, and get "Any referrer allowed", so it seems OK.
If I remove the key, I get OVER_QUERY_LIMIT.
Please advise.
Currently, the Google API Console cannot generate working API v3 browser keys for geocoding use at all, whether used via a JSON output URL or Javascript. This has been the case for at least the past 3 days.
Just as for Google Places a few months ago.
All you can do is ignore the error code 610, REQUEST_DENIED, and erroneous alerts, and wait for Google to fix it.
I'll be happy to change the accepted answer to one that describes how to contact Google about your Google Developer account, raise a ticket, register/pay for support, or similar.
we recently migrated our application (IIS Server + DB Server) to AWS and also modified the network architecture a little bit. The entry point of the system is an Astaro Firewall (we use the AWS AMI) which also host the SSL certificate of the web server. Everything related to the firewall has been done by a vendor and we only have some read-only privileges.
We are getting 403 errors in a few situations but I will explain one, as they all may be related.
We got a form which query the database and return a report in HTML format (this report also have some checkbox to do updates). The first time the form is submitted, we always get the report back. If we wanna post the form again, updated with new data, it crash, returning error 403. We noted that it doesn't crash when the first results returned a very low number of rows (or none).
Looking at the details of the POSTs in Developer Tools, what seems to be the only difference between a working and 403 error reply is the size of the data posted. The second post is always bigger because it contains the data of the first report (as the page have also other option to checkbox the rows).
Also, looking at the IIS logs we don't see any traces of the POST that crash. Nothing at all.
This problem happen only in production. In dev environment it's all working flawlessly. The only difference is that the production have the firewall/ssl, while development is all open. This is why we think it may be related to SSL.
The vendor is not the most helpful, we are looking for help to pinpoint the issue and trying to take the situation in our hands.
Any input appreciated.