As the subject line states, all API calls for the past 6 days have resulted in Error 400 ThrottleUser responses. Tried a new api key; pox, json and service connections.
Is this happening to everyone? Does anyone know how to tell them it is not working?
Support can be requested here: https://www.bing.com/webmaster/support
as suggested here: https://social.msdn.microsoft.com/Forums/en-US/f24edc35-5aab-445a-91b8-73a1982019d7/webmaster-api?forum=whatforum
Related
we are using CSOM to communicate with SharePoint Online.
Since April 16th, 2021 we recognize http 400 responses from different parts of our code using CSOM calls from time to time. We added status 400 to our internal retry logic. Executing the same call a few seconds later succeeds. So pretty much a wrong status code.
It seems like SharePoint should generate a 429 throttling response at that time and somehow generates an incorrect 400.
Does anybody else experience the same?
Regards
Sven
Microsoft has fixed the issue on May 7th as reported here: https://github.com/SharePoint/sp-dev-docs/issues/6955
We could not find any http 400 failures in our logs after 5/7, so the fix seems to work in our case.
I am currently trying to pull data from the Eventbrite API platform in Jupyter Labs. Sporadically, I am receiving a 406 Not Acceptable Error when I make the request. However, invariably, if I make the same request again a few minutes later the request pulls the data fine.
I've checked the usual things: ie that I have not gone over my request limits.
Here is the request I am currently making:
url = 'https://www.eventbriteapi.com/v3/events/search/?token=MY_TOKEN_HERE&location.latitude=42.34631505453378&location.longitude=-71.04174243961083&location.within=3km&start_date.range_start=2019-10-30T00:00:00Z&start_date.range_end=2019-11-30T00:00:00Z&expand=venue'
x = requests.get(url)
x
And the response:
<Response [406]>
Any thoughts on what the problem might be?
Yeah, I got an email from them a little over a week ago saying:
Hello,
We're reaching out today to follow up regarding the events/search/ endpoint. Thank you for your patience while we worked to reach a conclusion to the issue.
Access to the Eventbrite Event Search API (GET /v3/events/search/) will be shut down at 11:59 pm PT on Thursday, December 12, 2019.
We strongly encourage you to find and remove any code that makes requests to this Event Search API from your applications in advance.
Why is this happening?
We’re removing the Event Search API to further improve the Eventbrite platform and allow us to support more Creators and their events. Allowing public access to this particular API was impacting our platform and the high level of service we strive to provide to our creators and their attendees. We are able to provide alternative access to retrieve your event data through our Event APIs (see below).
What is the replacement API?
To get Events via our API, please see:
• Retrieve an Event by ID — GET /v3/events/:event_id/
• List Events by Venue — GET /v3/venues/:venue_id/events/
• List Events by Organization — GET /v3/organizations/:organization_id/events/
If you’re retrieving private events on behalf of another user, you can complete the app authorization flow. If you’re interested in retrieving public events on behalf of many Eventbrite creators, you can apply to our distribution partner program.
We apologize for the delay in communication regarding this decision, as well as for the inconvenience and frustration this change has caused
Regards,
Eventbrite Developer Support
So it looks like that's finally confirmed as dead at least.
FYI... this is an an ongoing Eventbrite API issue that is causing problems for many. See: https://groups.google.com/forum/#!topic/eventbrite-api/-E0MG7THMsc
I'm working the DocuSign API and I have an issue while trying to receive an update on how many and which users signed on my internet form. I have created Handler with SSL certificate that supposed to get information on streaming mode. but, when I'm trying to make the connection I get "forbidden 403" error.
If anyone has already experienced such a problem I will be pleased to get some assistance here.
Thanks in advance.
This question already exists:
Instagram/Facebook deprecating many APIs [duplicate]
Closed 4 years ago.
i am using wordpress site with the grid plugin, yesterday the plugin work great, i added new access token, today it start showing me this error
"Sorry, an error occurs from Instagram API: This endpoint has been retired
"
One more sudden change from Insatagram, few endpoints are deprecated immediately, It's effective from 4th April.
here is list of endpoints are
1) Follows and Relationships
2) Commenting on Public Content
3) Likes
4) User Search
Please see more details here
There is also some change in response of few APIs
https://www.instagram.com/developer/changelog/
Facebook retired most of Instagram's APIs today along with a lot of other locking-down in order to address privacy leaks. "This endpoint has been retired" (rather than something like "Unauthorized") suggests maybe you were bit by that. You can read more about it from Facebook.
The Bing Web Search API worked last week and at some point this week, it has been returning 403 errors. I don't know if anyone else has been encountering similar problems?
To replicate this, simply signup here with a bing account and you should get 5000 free queries per month. Below is a snippet of code (I believe I'm properly authenticated since putting in improper credentials fails gives a 401, rather than 403 error).
import requests
user = '...'
key = '...'
# 403 error
requests.get('https://api.datamarket.azure.com/Bing/Search/Web?Query=%27Xbox%27&$format=json', auth=(user, key))
# 401 error
requests.get('https://api.datamarket.azure.com/Bing/Search/Web?Query=%27Xbox%27&$format=json', auth=('a', 'b'))
Is anyone else getting this?
403 is the Forbidden status code. Your subscription probably expired or you exhausted your query limit.
Server errors are always in the 500-599 range. Errors in the 400-499 range are always client errors. If you repeatedly receive 500 errors, you should check Azure's status page to ensure there isn't a problem.
As a rule, you shouldn't assume that a major service like Bing Search is down and no-one noticed for days. It's far more likely that there is a problem with your account or your code, especially if you receive client error codes.