Hey Marcel, This is indeed a bug. When you try and create a list without a description, the API returns a status code of 200, and what looks like a successful response. However, the list is not fully created, and is not visible on twitter.com. If you then make the same creation call with a description added, the list becomes visible on twitter.com.
I tested this with curl and basic authentication 10 minutes ago. Tim. On Fri, Nov 20, 2009 at 3:31 AM, Nelu Lazar <[email protected]> wrote: > I confirm this behavior, but I just added the "description" field to > the input form and it works like a charm. And I find it useful as > well. > > - @NeluLazar > > > On Nov 19, 1:44 am, Rich <[email protected]> wrote: > > I can confirm this too, the lists are not being created without a > > description > > > > On Nov 19, 4:13 am, Naveen <[email protected]> wrote: > > > > > > > > > We are seeing this issue as well.. > > > > > We create a list with: > http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-POST-lists > > > > > This is returning all valid data with an id for the list, which > > > indicates it was successfully created.. > > > > > However when we try to get status for the list it is returning 404 > > > > > Then we try to get the lists using > > > > >http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-GET-lists > > > > > And it is not returned in the result, the newly created list is also > > > not on the twitter website.. > > > > > however if we include the description parameter(with empty content) > > > the list is created and returns expected data and does show up on the > > > twitter website.. > > > > > There is a bug here... The work around is to just include an empty > > > description field, which should not break anything in the future > > > either. > > > > > On Nov 18, 8:08 pm, Marcel Molina <[email protected]> wrote: > > > > > > The description parameter is not required to create a list. > > > > > > On Wed, Nov 18, 2009 at 3:57 PM, David <[email protected]> wrote: > > > > > I've been using the List api in my app, and just noticed that the > POST > > > > > method to /:user/lists.:format returned the correct response, but > > > > > didn't actually create a list. > > > > > > > I've been following this api document: > http://apiwiki.twitter.com/Twitter-REST-API-Method:-POST-lists > > > > > > > What I did notice was that the Add New List ui on Twitter.com has a > > > > > description field, and so I tried the same call with an additional > > > > > post param "description", and it worked. > > > > > > > The description param can be empty, but it is required to make this > > > > > call work. Might be a bug? > > > > > > > Just a heads up for anyone who might be wondering. > > > > > > > DC > > > > > > -- > > > > Marcel Molina > > > > Twitter Platform Teamhttp://twitter.com/noradio >
