Any updates? On Apr 15, 2:01 pm, ap <[email protected]> wrote: > I guess, essentially my question is: whats the best method to use to > get a Twitter User back, more specifically, the Twitter users' first > name and last name. > > On Apr 15, 1:53 pm, ap <[email protected]> wrote: > > > > > > > > > This will help you troubleshoot my (hopefully everyone else's) issue: > > > {Code} > > TwitterFactory factory = new TwitterFactory(); // Good > > Twitter twitter = factory.getInstance(); // Good > > > authenticatedUser = twitter.showUser("273610984"); // Throws errors > > {Code} > > > {Errors} > > Twitter{auth='OAuthAuthorization{consumerKey='IOnTxKfXbr8NuY8uBG8A6g', > > consumerSecret='******************************************', > > oauthToken=AccessToken{screenName='heller1900', userId=273610984}}'} > > TwitterException{statusCode=404, retryAfter=0, > > rateLimitStatus=RateLimitStatusJSONImpl{remainingHits=347, > > hourlyLimit=350, resetTimeInSeconds=1302892, secondsUntilReset=3440, > > resetTime=Fri Apr 15 14:43:16 EDT 2011}} > > 404:The URI requested is invalid or the resource requested, such as a > > user, does not exists. > > {"request":"\/1\/users\/show.json?screen_name=273610984","error":"Not > > found"} > > {Errors} > > > Thanks, > > -Ashish > > > On Apr 15, 1:41 pm, Taylor Singletary <[email protected]> > > wrote: > > > > If you can provide some more details, I can investigate possible issues. > > > What parts of the requests are failing? There are many steps involved, so > > > localizing to the specific areas where you're having problems will be very > > > useful. > > > > Make sure that when using OAuth, you're using api.twitter.com/oauth/* for > > > all paths and that when you're using the REST API you're using > > > api.twitter.com/1/* -- the subdomain matters for both areas of the API, > > > and > > > the version number is imperative for the REST API. > > > > @episod <http://twitter.com/episod> - Taylor Singletary > > > > On Fri, Apr 15, 2011 at 10:35 AM, m36tb6ll <[email protected]> wrote: > > > > > Hi- > > > > > same issue here... seems like the tokens are not matching.. > > > > > On Apr 16, 1:28 am, Taylor Singletary <[email protected]> > > > > wrote: > > > > > What kind of errors are you seeing? Do you have an example of the > > > > > status > > > > > code and body message? What specific endpoints throw the error? > > > > > > @episod <http://twitter.com/episod> - Taylor Singletary > > > > > > On Fri, Apr 15, 2011 at 10:23 AM, ap <[email protected]> wrote: > > > > > > Twitter API authentication throwing errors on all our sites. Any > > > > > > known > > > > > > issues that are not reflected on your API Status page? > > > > > > > Thanks, > > > > > > -Ashish > > > > > > > -- > > > > > > 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
