Http Status 429

Nov 1, 2013 at 12:05 AM
I completely refactored our code, and now using Tweetinvi library instead of the old API we were using, but it is giving me this error.
{System.Net.WebException: The remote server returned an error: (429) Client Error (429).
   at System.Net.HttpWebRequest.GetResponse()
   at oAuthConnection.OAuthToken.ExecuteQueryWithSpecificParameters(String url, HttpMethod httpMethod, WebExceptionHandlingDelegate exceptionHandler, IEnumerable`1 headers) in c:\Users\timart\Documents\My Box Files\Development\Tweetinvi\oAuthConnection\OAuthToken.cs:line 160
   at oAuthConnection.OAuthToken.ExecuteQuery(String url, HttpMethod httpMethod, WebExceptionHandlingDelegate exceptionHandler) in c:\Users\timart\Documents\My Box Files\Development\Tweetinvi\oAuthConnection\OAuthToken.cs:line 180
   
I believe this is happening because it is receiving too many requests. And achieving rate limit. So does that mean there is nothing we can do, other than to wait?
Coordinator
Nov 1, 2013 at 1:53 AM
When you need to perform too many request for a Token I tend to create new Tokens and use them to perform the actions I need.
  • Though you can note that all the limits on Twitter are not on posting but on retrieving information.
  • Twitter recommends that the developers use cache instead of requesting too much information.
  • If you are willing to follow in live an account you will prefer to use a UserStream instead of retrieving the Timeline every x secons
  • For the rate limits on twitter you can see the following documentation.
Please let me know what you want to do with your Token and why you need to perform too much queries comparing to the rate limit.

I hope this helps solving your problem.

Kind Regards,
Linvi
Nov 1, 2013 at 11:17 PM
Hi
as we have debugged through it, when i used a different set of OAUTH keys, they seem to work OK. I will try to see if i can get another set of OAUTH keys.

Thanks