I found it out myself. I was still using the old call to 
http://twitter.com/statuses

When I changed this to http://api.twitter.com/1/statuses it worked
fine, the unauthorized message disappeared.

Cheers,

Erik


On 7 ene, 14:28, Erik Bloem <ejbl...@gmail.com> wrote:
> thanks for your reply Deepa,
>
> so what do I have to do when I want to use a fixed PIN?
>
> The problem is that if I use oauth_verifier with a temporary token, it
> will ask me to connect to twitter and have to confirm that the
> application is allowed to connect to my account. That is not fiable in
> a permanent integration. Once accepted, it generates a PIN code. With
> this PIN code it must be possible somehow to connect to Twitter. What
> is the PIN code used for anyway?
>
> kindest regards and txs,
>
> Erik
>
> On 7 ene, 07:09, deepa nagaraj <deepa.23.naga...@gmail.com> wrote:
>
>
>
> > no you cannot do like that...
> > for each it will generate oauth_verifier.....
>
> > On Fri, Jan 7, 2011 at 5:32 PM, Erik Bloem <ejbl...@gmail.com> 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- Ocultar texto de la cita -
>
> > - Mostrar texto de la cita -- Ocultar texto de la cita -
>
> - Mostrar texto de la cita -

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