POST /tasks
Creates a new task and returns it as a JSON object.
Servers
- https://api.todoist.com/rest/v2
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
project_id |
String | No |
Task project ID. If not set, the task is put in the user's Inbox. |
parent_id |
String | No |
Parent task ID. |
due_string |
String | No |
Human-defined task due date (ex. "next Monday," "Tomorrow"). Value is set using local (not UTC) time. |
description |
String | No |
A description for the task. This value may contain markdown-formatted text and hyperlinks. |
labels[] |
Array | No |
The task's labels (a list of names that may represent either personal or shared labels). |
duration_unit |
String | No |
The unit of time that the duration field above represents. Must be either minute or day. If specified, duration must be defined as well. |
due_datetime |
String | No |
Specific date and time in RFC3339 format in UTC. |
section_id |
String | No |
ID of the section to put the task into. |
duration |
Integer | No |
A positive (greater than zero) integer for the amount of duration_unit the task will take. If specified, you must define a duration_unit. |
priority |
Integer | No |
Task priority from 1 (normal) to 4 (urgent). |
order |
Integer | No |
Non-zero integer value used by clients to sort tasks under the same parent. |
assignee_id |
String | No |
The responsible user ID (only applies to shared tasks). |
content |
String | No |
Task content. This value may contain markdown-formatted text and hyperlinks. |
due_lang |
String | No |
2-letter code specifying the language in case due_string is not written in English. |
due_date |
String | No |
Specific date in YYYY-MM-DD format relative to the user's timezone. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.