The API described in this document is obsolete. It is documented here only for the support of legacy applications that might be using it. New applications are encouraged to use the newer, REST-based API. Older applications, too, are encouraged to switch to the newer API.
Retrieves a specific todo-item by its numeric ID. This is useful for (e.g.) looking up the todo-item associated with a time-entry.
This call lets you add an item to an existing list. The item is added to the bottom of the list. If a person is responsible for the item, give their id as the party_id value. If a company is responsible, prefix their company id with a ‘c’ and use that as the party_id value. If the item has a person as the responsible party, you can use the notify key to indicate whether an email should be sent to that person to tell them about the assignment.
<request>
<content>#{content}</content>
<!-- if the item has a responsible party -->
<responsible-party>#{party_id}</responsible-party>
<notify>#{true|false}</notify>
<request>
<todo-item>
...
</todo-item>
Modifies an existing item. The values work much like the “create item” operation, so you should refer to that for a more detailed explanation.
<request>
<item>
<content>#{content}</content>
</item>
<!-- if the item has a responsible party -->
<responsible-party>#{party_id}</responsible-party>
<notify>#{true|false}</notify>
<request>
<todo-item>
...
</todo-item>
Deletes the specified item, removing it from its parent list.
<todo-item>
...
</todo-item>
Changes the position of an item within its parent list. It does not currently support reparenting an item. Position 1 is at the top of the list. Moving an item beyond the end of the list puts it at the bottom of the list.
<request>
<to>#{to}</to>
<request>
<todo-list>
...
</todo-list>
Marks the specified item as “complete”. If the item is already completed, this does nothing.
<todo-item>
...
</todo-item>
Marks the specified item as “uncomplete”. If the item is already uncompleted, this does nothing.
<todo-item>
...
</todo-item>