Calling the API (v1.1) URL appending web request (https://api.twitter.com/1.1/users/lookup.json?) does not seem to work.
I keep getting the error: The remote server returned an error: (401) Unauthorized.
I have tried several parameter combinations to appended to the “https://api.twitter.com/1.1/users/lookup.json” URL, including “?user_id=xxxxxxx”.
When making the API (v1.1) URL call to obtain twitter follower ID’s (https://api.twitter.com/1.1/followers/ids.json) works with the way I generated the authentication header. I create the authentication header the same way when attempting to get user information (GET users/lookup) when passing in the user_id (or several user_id 's), but it doesn’t seem to work. Maybe I am not including the correct parameters when making a request to the https://api.twitter.com/1.1/users/lookup.json for both the final result and for the generation of the signature.
So my questions are … what are the correct parameters in the requests for generating both the signature (oauth_signature) value and obtaining the fully-hydrated user objects information???
I noticed that in the API 1.1 documentation the only example given on the ‘Creating a signature’ page is one used to post a tweet (https://api.twitter.com/1/statuses/update.json). The information should include an example for creating a signature for all the API resources.