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,
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
This is what I get in the response
{request:\/friends\/ids.json?user_id=121552558,error:Incorrect
signature}
Kathy
On Dec 17, 1:28 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Kathy,
What is the error we are returning in the response body? It should contain
information about why the
I still get the same error 401 with url
https://api.twitter.com/1/friends/ids.json
Kathy
On Dec 17, 9:10 am, Tom van der Woerdt i...@tvdw.eu wrote:
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
Hi Kathy,
What is the error we are returning in the response body? It should contain
information about why the request failed.
Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Fri, Dec 17, 2010 at 11:14 AM, Kathy kathylee1...@gmail.com wrote:
I still get
