I issue an authenticated call to /venues/venue_id but I get a 500 error
"Foursquare servers are experiencing problems. Please retry and check
status.foursquare.com for updates."
I make about 60 of these calls, and only ~20 of them fail. It just started failing 3 days ago. Any ideas? What else do I need to provide?
Edit: The call I am making is:
https://api.foursquare.com/v2/venues/4ae2619bf964a520d58d21e3?oauth_token=xxxx&v=20120201
I make about 30 of these, and 10-12 work just fine, but the remaining fail. I tried the Foursquare API Explorer and I still get a 500 response.
My API requests suddenly started working. No word why.
Related
Two days ago, something changed and the RapidAPI endpoint of the Imgur API just stopped working for uploads.
Also, it seems Imgur isn't responding over at the RapidAPI discussions, so hopefully their engineers see this. There's a thread about it here. I have no idea why Imgur does not have a contact point for their paying customers though.
My website has worked just fine and let me upload stuff with no problems, but it just returns a 404 error on the https://imgur-apiv3.p.rapidapi.com/3/image endpoint now. No other errors or messages.
Seems like many developers are getting this error. This can fix the issue
Add the ?client_id=<imgur_client_id> query string parameter to API endpoint (POST /3/image).
However, you can always write to RapidAPI support team at support#rapidapi.ciom
I am using google search console's URL testing tools API for a while, and I am receiving a bunch of 502 bad gateway errors. I had submitted a quota increase request to bump up our default requests per day and described that we needed an increase in requests per minute (default is 60/minute). But unfortunately, google support has not responded yet. We are trying to call this API in parallel.
This is the error :
Request failed with status code 502
Could anyone help me understand this issue? I feel that we are exceeding the quota limits because 502 is usually associated with an issue while communicating with the upstream server.
I have reported the issue in Google's public issue tracker. Please add your feedback there.. https://issuetracker.google.com/issues/194021199
It is broken and only works some times. The worse part is that it reports back as HTTP 200 in the google console without any errors so they probably have no idea that it is even broken.
I wrote Python code that retrieves API json data from the haveibeenpwned v2 API. The code has been working flawlessly for a month or so but now when I run the code I get ERROR 503.
I searched online for the error code to my understanding this is usually caused by temporary overloading or maintenance on the server so I tried waiting. I've waited about a week trying 5-10 times a day and get the same error every time.
I used the requests Python module to retrieve the json data and to print the status code. If I get error 404 I know that the information isn't there and it goes through the loop until I get the 200 status code.
print(r.status_code)
Could this be a problem I can solve on my side or should I try to contact the owner of the API.
Edit: I realized that the website recently implemented CloudFlare DDoS protection. Could that impact the way I am trying to retrieve the data?
For a while it's been working fine. Now today, all of a sudden, when I try to list messages for a particular email address the API call just hangs for a while and then returns Backend Error (500). It still works sometimes, and sometimes it's just really slow at responding, but for the most part it seems to hang.
Any ideas what the problem could be, or how to diagnose it. I'm using the node, googleapis package, oauth2 tokens, server-side calls.
PS: I've checked the logs and there aren't any 4xx errors.
I use the Google weather API in my web site, and today I get an error that the API link doesn't return any data.
When I check the link directly I get an (Error 403).
Here is the link.
Can anyone please tell me a solution for this and provide me another link for the API?
Every now and then the API stops working for short periods of time, the last days more often a 403 is trown. For my site, last night it happened 13 times. But the site tries immediately again and the second or third time, the data loads without problems. As the API is unofficial, not sure what’s causing the 403.
Make sure you cache the data as the API will block your IP temporary when you make too much requests. In my case, I cache for 20 minutes and if no data can retrieved, the site will not try more than 10 times to reload the API. Once I forgot to turn caching on after debugging and as my site did many hundred requests (with every visitor), the IP was blocked within an hour. If a remember correct, the error was not a 403. Fortunately, the block lasts for less than a half day.
There is currently an intermittent 403 Forbidden response to the Google Weather API that you are using. See Google Weather API 403 Error
The reason for the intermittent 403 response is not known but has been a problem since the 7th of August 2012.