Re: [twitter-dev] Re: direct_messages/new

Chris, You should also be using 'user_id' instead of 'user' in the request that succeeds. Abraham - Abraham Williams | Hacker Advocate | abrah.am Just launched from Answerly : InboxQfor Chrome @abraham

Re: [twitter-dev] Re: direct_messages/new

Hey Chris, Looks like you're missing an "s" to direct_messages in the PHP code you're quoting. Would be interested to see your HTTP Response headers. Probably a 404 you got there. Arnaud / @rno On Wed, Apr 6, 2011 at 10:24 PM, Chris Teso wrote: > The Full http respon

Re: [twitter-dev] Re: direct_messages/new

I'm not able to reproduce this so could you share the base signature you are sending. The consumer_secret and user_secret are not included in those two pieces of data so can be shared here, but if you prefer you can directly email them to me. Best, @themattharris Developer Advocate, Twitter http:/

[twitter-dev] Re: direct_messages/new

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', ar