Many thanks for that - I've now got it working as intended. (I was,
in fact, completely misunderstanding which tokens were which!)
Much appreciated. :-)
All the best,
Rich.
On Fri, May 1, 2009 at 3:45 PM, jmathai jmat...@gmail.com wrote:
To get the access token you need to call /oauth/access_token. That'll
give you back tokens you can save and reuse. This is a good flow
diagram: http://oauth.net/core/diagram.png
On May 1, 4:46 am, Richard L richard.lockw...@gmail.com wrote:
Hi,
I've looked through the FAQ, archives and other websites, and haven't
found anything that has helped on this, so apologies if I've just
missed it!
I'm building an application which needs to be able to set a user's
status automatically, without that user needing to log in and approve
it every time.
I'm using a variation on the code
at:http://www.voiceoftech.com/swhitley/?p=681
, and it's working - to an extent.
A user can visit a page on my apphttp://www.mytwitterapp.com/twitter.aspx,
be redirected to Twitter to approve the app, then be sent back to my
app, to the page which now has the
form:http://www.mytwitterapp.com/twitter.aspx?oauth_token=EQ8Mi7T2Xqi6y5Ka...
I can then use that token to get the token secret and interact with
Twitter (primarily setting a status update).
However, if I try to use that token again, I get a (401)
Unauthorized error.
I thought that the oauth_token that gets returned
fromhttp://twitter.com/oauth/authorizewas a token that I could store, and
use to repeatedly access Twitter when needed. It seems that what I'm
actually getting back is an Access Token. So, my questions are:
1. Does what I've written above make sense?
2. Is there a token I can store, and use to repeatedly access Twitter
- and if so, how can I get that value?
3. Am I barking up the wrong tree entirely?
4. Anything else you think might be of help!!
Many thanks in advance,
Richard.
