Ah, ok. The header allows you to make one (1) call to Twitter, usually
the verify_credentials.json page. This allows you to verify that the
user has a Twitter account (and even get some information about the
user), but it will not allow you to send messages etc.
OAuth Echo is nothing more than a
Hey Tom,
I think I am falling into this pitfall myself. I don't have the users
information only the information that the iPhone twitter app sends me
for posting an image on a custom end point. With that header
information they send should be enough to send back to twitter to get
the user
Hello Shob,
Do you have already run the Twitter status update?
Maybe i have the same problem.
Regards,
Dennis
On 6 jul, 16:10, Jacky jaga...@gmail.com wrote:
Hullo,
POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
%2Frequest_tokenoauth_callback%3Doob%26oauth_consumer_key
Also,
OAuth
oauth_consumer_key=
instead of
Oauth
oauth_consumer_key=...
in the authorization header as per Taylor, thanks...
It might be a good idea to be able to use this REST client for all
commands as a test benchmark for Twitter API calls(just a thought)...
(I have not tested much on this yet, I am just looking at it)...
https://addons.mozilla.org/en-US/firefox/addon/9780/
Shob
On Jul 8, 1:22 pm, Jacky
Hullo Matt,
Thanks for the reply...
I'm too far down this road to take detours...I've got everything
working except the final step...everything else checks in well..
I'm just hung up on the objhttp load using vba, somehow the stream
loaded seems to fail the generated signature (signature has been
Instead I launched it through a browser and I am all ok.
(P.S. Incidental, but, on my previous post I made a typo in the post,
i.e.,not the very first string, but the second string and it already
has the Oauth in front already and that is the string)
Thanks though,
Regards,
Shob
On Jul 7,
