Per this announcement:

I'm changing my code to use the new routes. When I do something like:{list ID}
&screen_name={screen name} or{list
ID}&user_id={user ID} 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...{slug}&screen_name={screen
name} or{slug}&user_id={user
ID} 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

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:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:

Reply via email to