Hi David, This is mostly a documentation error.. but it really depends on how you turn your head and look at it. This method does accept include_entities=true as an argument -- but direct messages are not currently enabled to contain entities.
It's like a telephone booth that doesn't have a connection -- it'll still take your change, but it won't make a call :) Taylor On Tue, Nov 16, 2010 at 3:25 PM, David W <d_wy...@yahoo.com> wrote: > I think I'm going to raise a ticket on this if no-one has any bright > ideas? > > Cheers, > dw. > > On Nov 12, 10:54 am, David W <d_wy...@yahoo.com> wrote: > > I'm looking at thehttp://api.twitter.com/version/direct_messages.json > > API and the documentation states that it supports the include_entities > > parameter, but no matter what I do I don't seem to get any entity data > > back in the response. > > > > I'm testing with the Apigee API Console and using the following > > request: > http://api.twitter.com/1/direct_messages.json?include_entities=true > > > > Am I missing a trick, is the documentation wrong, or is there a > > problem? > > > > Thanks in advance. > > -- > 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