Cannot pass a comma separated list without breaking OAuth?


#1

https://dev.twitter.com/docs/api/1.1/get/users/lookup

So on this part of the documentation, it states the following:

screen_name: A comma separated list of screen names, up to 100 are allowed in a single request. You are strongly encouraged to use a POST for larger (up to 100 screen names) requests. Example Values: twitterapi,twitter https://api.twitter.com/1.1/users/lookup.json?screen_name=twitterapi,twitter

Now, connecting to user lookup with the following request:

"https://api.twitter.com/1.1/users/lookup.json?screen_name=FT" 
"Content-Type"  :  "application/x-www-form-urlencoded" 
"Authorization"  :  "OAuth oauth_consumer_key="XXXXXXXXXXXXXXXXX",
oauth_token="XXXXXXXXXXXXXXXXXXXXXXX",
oauth_signature_method="HMAC-SHA1",
oauth_signature="XXXXXXXXXXXXX",
oauth_timestamp="1379001175",
oauth_nonce="19EwayGhef9OLDzu",
oauth_version="1.0"" 

I get a good response and get a user object for the account @FT.
Yet, when I connect to:

"https://api.twitter.com/1.1/users/lookup.json?screen_name=FT,MTV" 
"Content-Type"  :  "application/x-www-form-urlencoded" 
"Authorization"  :  "OAuth oauth_consumer_key="XXXXXXXXXXXXXXXXXXXXXXXXX",
oauth_token="XXXXXXXXXXXXXXXXXXXXXXXXXXX",
oauth_signature_method="HMAC-SHA1",
oauth_signature="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
oauth_timestamp="1379001281",
oauth_nonce="BoGLJNOKRmh7s9R8",
oauth_version="1.0"" 

I receive the following message:
"{“errors”:[{“message”:“Could not authenticate you”,“code”:32}]}"

I have no idea why this is, I have also tried percent encoding my screen_name arguments, such that the comma becomes %2C with no luck, infact, I get the response
"{“errors”:[{“message”:“Sorry, that page does not exist”,“code”:34}]}"

Please advise


#2

Solved:
So I was adding to the url a simple string query argument. This is not sufficient.
I returned and reused percent encoding but this time added an encoded query item instead of a normal query item. This produced the expected outcome.