Yeah thats fine, actually it works fine if you change it to JSON, it's only the XML endpoint that seems to be broken, but seeing as all other status api's have both JSON and XML I would hope this would too
On Oct 7, 3:03 pm, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > I'm not familiar with that error yet, but will look into it. > > Related results, and a number of the other new APIs, are still relatively > unstable. They will be unavailable at times, and are not necessarily > prepared for widespread use yet. Early adopters will have to tolerate a > certain amount of mystery from them. > > Taylor > > On Thu, Oct 7, 2010 at 2:06 AM, Rich <rhyl...@gmail.com> wrote: > > Hi > > > I'm trying to implement the related tweets feature, and the screen > > name I'm testing from does have access to #newtwitter as described in > > the pinned post at the top. > > > The URL I'm trying is > > >http://api.twitter.com/1/related_results/show/26630532248.xml?include... > > but whenever I call it I get an HTTP 406 error back. > > > Can anyone shed some light on what might be causing it? > > > Richard > > > -- > > 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
