Re: [twitter-dev] direct_messages/new

[Arnaud Meunier]

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 



On Tue, Apr 5, 2011 at 4:34 PM, Chris Teso  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

Re: [twitter-dev] direct_messages/new giving error 'Incorrect signature'

[Scott Wilcox]

I'd guess that you're not encoded the message content properly. 

On 28 Feb 2011, at 08:10, BITS wrote:

> Hello,
> 
> I want to sent private message to followers. I am using
> direct_messages/new for this.
> 
> It is giving error response as
> 
> Array
> (
>[request] => /direct_messages/new.json
>[error] => Incorrect signature
> )
> 
> Any solution?

-- 
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