creating oauth signatures is annoyingly subtle, isn't it?  i would suggest
playing with

verifying the signature base string and signature you're generating to what
that emits.

On Mon, Apr 12, 2010 at 9:10 AM, ryan baldwin <> wrote:

> I'm having a heck of a time getting the users/lookup to work. I keep
> getting an "invalid signature" response, however if I try hitting
> other urls that require authentication (such as statuses/
> home_timeline) I get the proper response.
> The only difference that I can see is that the users/lookup requires a
> comma separated screen_name param. An example of a call I'm making is
> as follows:
> The above produces a 401.  I though perhaps it's because the commas
> need to be encoded (however the examples I've seen that doesn't seem
> to be the case). Even if I tried sending up only 1 screen_name,
> however, it still fails with a 401.
> Like I said, if I hit up the statuses/home_timeline endpoint it works
> fine.
> Anybody have any idears?
> Thanks!

Raffi Krikorian
Twitter Platform Team

Reply via email to