Thanks Matt. I changed as you suggeted, making my baseString:
POSThttp%3A%2F%2Fapi.twitter.com%2F1%2Fusers
%2Flookup.jsonoauth_consumer_key%3DT5nsfaBaAg
%26oauth_nonce%3DzIImL4%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1289231301%26oauth_token%3D219-
If you get that error, your best option is to re-create the application
and use ReadWrite from the start. Your current keys probably are still
read-only, as they don't change if you change it on dev.twitter.com
Tom
On 11/9/10 4:30 PM, EL wrote:
Thanks Matt. I changed as you suggeted, making my
Thanks guys - deleting and recreating the application worked. Finally
got this solved! Hoorah! :)
Thanks for the assistance
On Nov 9, 3:31 pm, Tom van der Woerdt i...@tvdw.eu wrote:
If you get that error, your best option is to re-create the application
and use ReadWrite from the start. Your
In the basestring the encoded POST parameters are encoded again. This means the
%2C for the comma should be encoded too, making it %252C in the basestring.
Give that a try and let us know how it goes.
Best,
@themattharris
On Nov 7, 2010, at 23:51, EL lee@gmail.com wrote:
Still struggling
Still struggling with this. Been playing around with all the
parameters but cannot seem to authenticate these requests.
Anyone able to suggest any cause?
Thanks
On Nov 3, 8:47 am, EL lee@gmail.com wrote:
Thanks. I took the square brackets out, but still get back:
{error:Incorrect
Thanks. I took the square brackets out, but still get back:
{error:Incorrect signature,request:\/1\/users\/lookup.json}
TEST_IDS now encodes to:
21295828%2C20138230%2C15799970%2C12304722%2C39765560
and my baseString now comprises of:
POSThttp%3A%2F%2Fapi.twitter.com%2F1%2Fusers
