Per this announcement: 
http://groups.google.com/group/twitter-api-announce/browse_thread/thread/6f734611ac57e281?pli=1

I'm changing my code to use the new routes. When I do something like:

https://api.twitter.com/1/lists/show.json?list_id={list ID}
&screen_name={screen name} or 
https://api.twitter.com/1/lists/show.json?list_id={list
ID}&user_id={user ID}

...it works fine. In fact, it seems that the screen_name and user_id
are optional when using a list ID (because the list ID is unique on
its own?).

But if I do this...

https://api.twitter.com/1/lists/show.json?slug={slug}&screen_name={screen
name} or https://api.twitter.com/1/lists/show.json?slug={slug}&user_id={user
ID}

...it doesn't work. I've tried it for several different list slugs,
both public and private, and no dice. Every time I get an HTTP 400
response.

Per that announcement, shouldn't it work if I give it the list slug
and either a user ID or screen name?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to