On a get of the DIRECT MESSAGES (response)

<hash>
  <error>Incorrect signature</error>
  <request>/1/direct_messages.xml?
page=1&amp;oauth_consumer_key=XXXXXX&amp;oauth_nonce=9F8A26E63EE0F990765DBA32C5B67F60&amp;oauth_signature_method=HMAC-
SHA1&amp;oauth_signature=IXRybwcP7Z5Wt3IRcFxW1FOjhGo
%3D&amp;oauth_timestamp=1289346103&amp;oauth_token=XXXXXX&amp;oauth_version=1.0</
request>
</hash>


Anything that sticks out?


On Nov 8, 1:43 am, udta <[email protected]> wrote:
> No code, No answer....
>
> What is the lib you are using?
> Maybe the post body's urlencoding is wrong.
> Maybe you will meet the same problem when friendship create...
>
> At 2010-11-08 13:20:13,DavidD <[email protected]> wrote:
>
>
>
>
>
>
>
> >Also Favorites works fine.  No errors.   I'm not sure why this works
> >and direct_messages doesn't, nor will destroy on a status id
>
> >I really am at a loss here.   Can no one give me a pointer as to my
> >problem?
>
> >Are there any issues with these api's?
>
> >David
>
> >On Nov 6, 5:39 pm, DavidD <[email protected]> wrote:
> >> I am getting an 401 Unauthorized with an "Incorrect Signature" or
> >> "Could not authenticate" error when trying to get Direct Messages
> >> after getting an access token
>
> >> I can get a user_timeline no problem and I believe favorites but the
> >> Direct Messages and home_timeline I get an error.
>
> >> I also have a 401 when I try and delete a tweet from the user
> >> timeline.
>
> >> I am stuck and need help.
>
> >> Thanks!
>
> >> David
>
> >--
> >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

Reply via email to