OK thanks for the response. It's a shame that devs still need to roll their own (potentially inconsistent) link parsing logic for DMs and Search when the code is sitting somewhere within the Twitter codebase. :) The Entities on other timelines works really well for us.
Hopefully one for the future? Cheers, dw. On Nov 16, 11:31 pm, Matt Harris <thematthar...@twitter.com> wrote: > Hi David, > > This is known issue and there is a ticket filed for it here: > http://code.google.com/p/twitter-api/issues/detail?id=1967 > > Best > @themattharris > Developer Advocate, Twitterhttp://twitter.com/themattharris > > 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
