Hi Toddy, Something like pastebin is a good place to put example code/responses. Alternatively I post messages using an email client, and can post code without any problems -- maybe that will work for you?
The API works on rate limits so ensure you stay within them. Also back off if you keep getting error responses. Constantly breaking the rate limit and ignoring multiple error responses could mean you get blacklisted. But if you are just running some testing code manually it is unlikely this will happen to you. Making multiple requests to the same method won't affect you're rate limit anymore than a request to another rate limited endpoint. If you can share the log we can take a look and see if anything odd shows up. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Tue, Jan 25, 2011 at 11:10 PM, ToddySM <todd...@gmail.com> wrote: > Hi Matt, > > I looked at the logs from my application and it seems that each call > to lookup fails. Interestingly it seems there is another issue that > suggests I post to this group for investigation. Is there any way I > can send you the messages (apparently Google doesn't allow me to post > the full error message)? > > By the way I have question - what is the retry policy for the APIs? Is > the retry counted as a new call? Also, is there any chance that my > application gets throttled even more because it makes frequent calls > to lookup? > > Thanks! > Toddy > > > On Jan 18, 5:13 pm, Matt Harris <thematthar...@twitter.com> wrote: > > Hi Toddy, > > > > The users/lookup method, which lookupUsers calls, will only return that > > error if none of the user_ids/screen_names you provide are recognised. > The > > behavior of the API method is such that only the recognised > > user_ids/screen_names are returned and any which are not found are left > out > > of the response. > > > > As this method is a lookup by user_id or screen_name you can compare the > > returned user_ids/screen_names with the ones you queried for. Those that > are > > missing from the response were not found in our user database. > > > > You can find more information on the method in our developer > documentation: > > http://dev.twitter.com/doc/get/users/lookup > > > > Best, > > @themattharris > > Developer Advocate, Twitterhttp://twitter.com/themattharris > > > > > > > > On Tue, Jan 18, 2011 at 4:00 PM, ToddySM <todd...@gmail.com> wrote: > > > Hello, > > > > > I am trying to use lookupUsers(int[]) but occasionally I > > > receive the following exception: > > > > > 404:The URI requested is invalid or the resource requested, such as a > > > user, does not exists. > > > {"errors":[{"code":17,"message":"No user matches for specified > > > terms"}]} > > > TwitterException{exceptionCode=[47354327-0118689f], statusCode=404, > > > retryAfter=0, > > > rateLimitStatus=RateLimitStatusJSONImpl{remainingHits=167, > > > hourlyLimit=350, resetTimeInSeconds=1295247, secondsUntilReset=1658, > > > resetTime=Mon Jan 17 07:01:03 UTC 2011}, version=2.1.7} > > > at > > > twitter4j.internal.http.HttpClientImpl.request(HttpClientImpl.java: > > > 311) > > > at > > > > twitter4j.internal.http.HttpClientWrapper.request(HttpClientWrapper.java: > > > 72) > > > at > > > twitter4j.internal.http.HttpClientWrapper.get(HttpClientWrapper.java: > > > 86) > > > at twitter4j.Twitter.lookupUsers(Twitter.java:614) > > > > > The two questions I have are: > > > 1.) Does this mean that the whole batch failed? > > > 2.) How can I get information which user actually fails the call? > > > > > Thank you very much for the help. > > > ToddySM > > > > > -- > > > 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 > -- 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
