Search API rate limiting is not handled like other endpoints of the REST API. As explained on http://dev.twitter.com/pages/rate-limiting#search, the Search Rate Limit isn't made public to discourage unnecessary search usage.
Concerning the User-Agent, use something like "Your App Name - Version" (it should be unique). Including an HTTP Referer (i.e. "about page" of your app) is also a good practice :) Arnaud / @rno <http://twitter.com/rno> On Sat, Apr 2, 2011 at 10:05 PM, sduffer <shwetha.ga...@gmail.com> wrote: > Hi Team, > I am using grackle client to retrieve results from search api of > twitter. i am passing oauth parameter to retrieve 350 requests per > hour. Though I am doing it right it still retrieves me only 150 > requests per hour. I tried to verify account/verify_credentials and > found i am passing the correction oauth params. > Here is my dev code with Grackle gem > > twitter_client = Grackle::Client.new(:auth=>{ > :type=>:oauth, > :consumer_key=>'key, > :consumer_secret=>'secret', > :token=> 'token', > :token_secret=> 'xxxx' > }, > :headers => {"User-Agent" => "example.com"}) > > I am passing User-Agent as I have seen it mentioned in rate limit api > if it is correctly passed we can retrieve 350 requests per hour. > Could you let me know if I am mssing something or should pass anything > with Grackle api call to get 350 requests per hour using oauth. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
