Re: [twitter-dev] Unauthorized 401
no you cannot do like that... for each request it will generate new oauth_verifier. On Fri, Jan 7, 2011 at 5:32 PM, Erik Bloem wrote: > Hi to all, > > when I use a temporary oauth_verifier in a oauth/access_token call, it > works ok. Nevertheless, when I use a fixed PIN code obtained, it fails > with an Unauthorized exception. > > What could this mean? > > PIN is wrong? > Do I need to use another call, or use another parameter for the PIN > and not the oauth_verifier? > > Thanks for any reply, > > Erik > > -- > 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 > -- Regards, Deepa -- 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] Unauthorized 401
no you cannot do like that... for each it will generate oauth_verifier. On Fri, Jan 7, 2011 at 5:32 PM, Erik Bloem wrote: > Hi to all, > > when I use a temporary oauth_verifier in a oauth/access_token call, it > works ok. Nevertheless, when I use a fixed PIN code obtained, it fails > with an Unauthorized exception. > > What could this mean? > > PIN is wrong? > Do I need to use another call, or use another parameter for the PIN > and not the oauth_verifier? > > Thanks for any reply, > > Erik > > -- > 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 > -- Regards, Deepa -- 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] Unauthorized 401 http://twitter.com/friends/ids.json
Your url is wrong. Instead, use : https://api.twitter.com/1/friends/ids.json Tom On 12/17/10 2:06 AM, Kathy wrote: I keep getting unauthorized 401 error. I have been running my twitter application for months. But past couple of days, I was able to retieve very few friends information. Since Dec. 15, 6pm, I haven't been able to retrieve any. My search url is : http://twitter.com/friends/ids.json?user_id= -- 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] Unauthorized 401
No, you don't need authorization for that.
To help you debug these issues, we need these values :
* Your request (it's safe to include everything you replaced with
#keyvalue#, just don't include any "secrets" (keys are fine))
* The Base String used to generate the signature
Tom
On 12/16/10 5:26 PM, Erik Bloem wrote:
Hi,
I am trying to establish my first connection to twitter using .NET. I
get the following error when I use the demo project from internet that
is using a webrequest: "Unauthorized".
{http://twitter.com/oauth/request_token?oauth_callback=http://
localhost&oauth_consumer_key=#keyvalue#&oauth_nonce=#keyvalue#&oauth_signature_method=HMAC-
SHA1&oauth_timestamp=#keyvalue#&oauth_version=1.0&oauth_signature=#keyvalue#}
(I replaced the real values by #keyvalue# )
I created my app in dev.twitter.com and used the consumer key and
consumer secret from there.
Anybody knows what could be the reason. I read somewhere I would need
authorization by sending a mail to a...@twitter.com. Is this true? Or
could the reason be something else?
Thank you very much in advance for any response,
Erik
--
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
