The Full http response is NULL. The request sent is $this->connection->post('direct_message/new', array( 'screen_name' => $username, 'text' => $text ) ) with proper auth headers.
Again, the method works if we pass user_id rather than screen_name. $this->connection->post( 'direct_messages/new', array( 'user' => 19081905, 'text' => $text ) ); Using screen_name has been working for 4 months in our app, and stopped working 2 days ago. Thanks On Apr 5, 10:02 pm, Arnaud Meunier <arn...@twitter.com> wrote: > Hey Chris, > > The endpoint is working fine with both parameters (just tested it). > > If you're still having this issue, think to provide more details (i.e. > request sent with auth headers + Full HTTP response). Otherwise, people of > this Mailing List won't be able to help you that much! > > Arnaud / @rno <http://twitter.com/rno>On Tue, Apr 5, 2011 at 4:34 PM, Chris > Teso <christ...@gmail.com> wrote: > > direct_messages/new seems to have stopped working if using > > screen_name. > > > The method works if passing user_id. > > > Can you confirm either way? > > > -- > > 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