I have no idea why :user is used, although I can imagine that it has
something to do with accounts that are managed by multiple people
(contributors) or something. To be honest, I have no idea at all.

To answer your question about the best source of API documentation:
dev.twitter.com, and if you can't find it there, Google. Of course,
you can always ask it on this list.


On Aug 6, 10:58 am, Ken <k...@cimas.ch> wrote:
> I'd like some help as I implement and test the API methods, of which
> there are dozens.
> For example, the "create list" method, titled "POST :user/lists" on
> dev.twitter.com, shows the URL endpoint 
> as:http://api.twitter.com/version/:user/lists.format
> I am not familiar with the notation ":user" but from the example I
> guess that means we need to insert the screen_name or id here. We
> don't keep screen name, only ids, so I wondered if that would work. By
> mistake I used a user id that was not the same as the authenticated
> user. Result was, the authenticated user got a new list. The user
> whose id was sent in the URL was unaffected. Then i tried sending one
> with some junk in place of the user and got this error:
> <?xml version="1.0" encoding="UTF-8"?>
> <hash>
>   <request>/1/jdsflfj/lists.xml</request>
>   <error>Not found</error>
> </hash>
> Why are we sending :user ?
> I guess my question is, in order to economize on time, what is the
> best source of API documentation?

Reply via email to