I’ve been having issues adding members to a list using either “lists/members/create_all” or “lists/members/create”.
It’s basically a small app witch takes an array of ID’s and adds to a list belonging to the authorised user.
It’ll take the array and break into chunks of 50 and submit to “/create_all”. If the expected return doesn’t match then it’ll try again before taking that same list and submitting individually to “/create” to exclude any accounts that are blocked or don’t exist.
After a couple of submissions the “/create_all” returns:
404 {"errors":[{"message":"Sorry, that page does not exist","code":34}]}
And the submissions to “/create” return:
403 {"errors"[{'message':"You aren't allowed to add members to this list","code": 104}]}
The list belongs to the authorising user, the list is nowhere near full and none of the members being added have blocked the authorising account.
What’s also interesting, is that after these messages appear, the authorising account can’t even add members via Twitter.com.
Is there some kind of internal and unpublished rate limit being hit? Surely not with less than 80 members. Am I submitting too quickly (i.e. being reported for hammering the system). I do repeat the above tasks because of the lack of meaningful responses (I found that submitting a list to /create_all might add 47 members one moment and 50 another).
Does anyone have any idea what might be going on and perhaps a solution/workaround to effectively submit members without triggering a temporary block (assuming that’s what’s going on).
Many thanks
Justin
