Version 1.1
/Mobile/projects/tasklists/add
Inputs
Input | Input Definition | Required | Detailed Description |
pid | The associated project id | Yes | |
mid | The associated milestone id | No | |
name | The name of the tasklist | Yes | |
desc | The description of the tasklist | No | |
access | -------- | No | |
type | used to determine JSON or XML | No | If parameter is not passed than it will assume JSON. |
sid | The user's session id | Yes | If you do not pass a user session then no action can be taken. See the session debug section for disabling the session for debuging. |
While you can pass sid as GET parameter you are also welcome and recommended to pass it via POST for more security.
Ouputs
Response | Response Definition | Detailed Description |
statusCode | The status code for the returned result. (In this case should always be Success | |
statusMessage | The message that describes the associated status code. | |
id | The tasklist id | The new id for the tasklist |
pid | The project id | |
mid | The milestone id | |
name | The name of the new tasklist | |
desc | The description of your new tasklist | |
start | The start date of your new tasklist | this is populated for you. |
Access | Access variable | Not sure what this does but apparently its numeric, defaults to 0 |
Sample Outputs
JSON
{"response":
{"status":
{"statusCode":"1",
"statusMessage":"Success!"},
"tasklist":
{"id":"84",
"name":"Sample Tasklist",
"desc":"My tasklist Description",
"start":"123456789",
"access":"0"}
}
}
XML
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>
<statusCode>1</statusCode>
<statusMessage>Success!</statusMessage>
</status>
<tasklist>
<id>84</id>
<name>Sample Tasklist</name>
<desc>My tasklist Description</desc>
<start>123456789</start>
<access>0</access>
</tasklist>
</response>