Skip to main content
To create a task, you will need to provide the POST /tasks API with the action for the task, as well as an item to represent the file to add the task to. 
curl -i -X POST "https://api.box.com/2.0/tasks" \
     -H "authorization: Bearer <ACCESS_TOKEN>" \
     -H "content-type: application/json" \
     -d '{
       "item": {
         "id": "11446498",
         "type": "file"
       },
       "action": "review"
     }'

​
Task actions

Box currently supports two types of tasks defined by the action value: review tasks and complete tasks. The type of task determines the possible resolution states a task can be in and the interface shown to a user in the web and mobile apps.
Task actionPossible resolution states
reviewincomplete, approved, rejected
completeincomplete, complete
A review task starts out in an incomplete state and can be marked as incomplete, approved, or rejected. In the user interface a user is provided with a text box and an pair of buttons to approve or reject the task. A complete task starts out in an incomplete state and can be marked incomplete or completed. Once a this task is marked completed, no further changes can be made to the task’s state. In the user interface a user is provided with a text box and an button to mark the task as completed.

​
Completion rules

A task on a file can be assigned to more than one collaborator on the file, and a task has a completion_rule that can be used to define if all users who’ve been assigned the task (all_assignees) or only one assignee (any_assignee) need to complete the task.