My soundcloud app (that makes quite a lot of requests) recently started receiving the error:
429 - Too Many Requests
for all DELETE commands (when I attempt to delete a follow relationship). This was working perfectly last week. Do throttling limits exist for soundcloud api requests? I looked through the developer's guide but haven't found anything yet. The support page said to post a question here.
A 429 Status indicates that your application is making too many requests to the /me/followings endpoint. This isn't throttling per say, but an attempt to circumvent follow-spam applications.
How many requests are you making and with what frequency? If you back off for a while, are you able to get a successful response?
Related
A client is using Coschedule to push updates to LinkedIn via their employees' profiles. They noticed recently that Coschedule is giving error messages when they try to push updates to employee pages. The Coschedule technical team did some digging and determined it's an issue with LinkedIn's API, which they believe may have been updated recently (?).
Errors started occurring a couple weeks ago, the app was previously running fine.
They are hoping for more information on LinkedIn's API / how to resolve this as soon as possible as it's generating multiple error message and error emails per employee per day.
Thanks!
Tia
The outage we saw a few weeks ago was due to LinkedIn depricating the version of OAuth we used to connect LinkedIn profiles/company pages to Calendars. We've since switched to OAuth2, and if your client or your team is still having issues and seeing authentication errors when trying to send out messages, we recommend doing a hard reset of those LinkedIn profiles: https://help.coschedule.com/hc/en-us/articles/216529237-Hard-Reauthentication-for-Social-Profiles-When-Auth-Token-Keeps-Failing#LinkedIn
Best practice is to use an incognito browser window as well.
If you're still getting stuck, reach out to our support channel (support#coschedule.com)and we would be happy to take a closer look!
hello amadeus users i'm facing this problem
i'm amadeus beginner
when i started to use amadues sandbox php client
the system worked for me for about an hour then this error appeared from yesterday
this error appears in php and in site page
is this system related to my code or my api or general network failure
Our API platform is currently going through a maintenance check. Some APIs may get disrupted during that time. The platform will be available again in a short time.
I was able to connect to the LinkedIn API for about two months and everything was correct. Was wondering if there has been any change to the API lately to block my app like so?
The app was in development stage and mostly 5 hits a day against their API.
It's not you, it's LinkedIn. See others complaining about the same issue: https://twitter.com/search?q=linkedin%20oauth
Scenario: Spotify user on the native desktop application is adding and removing songs from the currently playing playlist.
I'm curious if it's possible for me to detect when any addition/removal happens? Basically need a trigger to tell me the playlist has changed without having to continuously poll Spotify's API to see if anything changed. Looking for a solution that could be used either via the Spotify API or something hack-ish using spotilocal or listening on Spotify's 4070 port.
Looking for a solution that could be used either via the Spotify API
or something hack-ish using spotilocal or listening on Spotify's 4070
port.
I wouldn't recommend this approach since the mentioned APIs may change without notice. It's not publicly supported so there's no commitment from Spotify to avoid breaking changes. It also requires the user to have the Spotify desktop application installed.
As you've noticed, since there's currently no way to subscribe to changes in a playlist, e.g. by a Websocket or HTTP PubSub interface like PubSubHubbub, your application would be forced to poll for changes. If you go down this path, I strongly recommend that you make use of the ETags and snapshot_id provided in the Playlist response.
Declaring how ETags are implemented in the Web API deserves a longer response and should be on the developer site. There's however a useful Working With Playlists guide on there that explains snapshots and some other things related to playlists.
It's also worth mentioning that all applications are rate limited, so I urge anyone polling to be aware of this and poll less rather than more. Obviously only poll when the application is actively used by the user, and only poll the playlist if it's actively viewed. You know you're being rate limited if you retrieve a 429 Too Many Requests response.
our website based on Instagram API recently sometimes encounters Instagram API's error response of "504 Gateway Time-out", we are a honest website and not abusing the API, why is this happening?
It seems to be an issue at Instagram. We have been receiving the same issue intermittently since the 3rd May. A quick search on twitter will show you that the same thing is happening to many other people around the world recently:
https://twitter.com/search?q=Instagram%20504%20gateway
The error itself is because an Instagram server not responding to the request from the load balancer or gateway (nginx in this case) in time, which leads to the gateway sending you the 504 error. This is usually caused by load on the web server or database, network routing issue or software error.
You can read the status code definitions here:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
Instagram will have to fix this issue, you can file a bug report here:
https://help.instagram.com/contact/364531043625021