Skip to main content
POST
Create a new task

Authorizations

Authorization
string
header
required

JWT token obtained from /v2/auth/login. Send it in the header: Authorization: Bearer <your_token>

Body

application/json
title
string
required

Title shown on the task card.

Example:

"Document task creation"

description
string

Detailed task description.

Example:

"Add request fields, response schema, and examples for POST /v2/tasks."

client_id
integer

Client ID linked to the task. It must belong to the authenticated account.

Example:

42

responsible_id
integer

Primary responsible user ID.

Example:

17

due_date
string<date-time>

Desired due date in ISO 8601 format.

Example:

"2026-05-20T18:00:00.000Z"

start_date
string<date-time>

Planned start date in ISO 8601 format.

Example:

"2026-05-19T12:00:00.000Z"

finished_at
string<date-time>

Completion timestamp in ISO 8601 format.

Example:

"2026-05-21T21:30:00.000Z"

end_date
string<date-time>

Planned end date in ISO 8601 format.

Example:

"2026-05-30T18:00:00.000Z"

status
integer

Numeric task status. When omitted, the API uses 0.

Example:

0

urgency
string

Urgency label. When omitted, the API uses the raw value Baixa.

Example:

"Alta"

estimated_time
string

Estimated effort in HHH:MM format.

Example:

"008:00"

budget
string

Budgeted effort in HHH:MM format.

Example:

"012:00"

project_id
integer

Project ID for the task.

Example:

8

column_id
integer

Column ID where the task should be created. If omitted with project_id, the API uses the first project column.

Example:

31

competence
integer

Competence linked to the task, when applicable.

Example:

202605

type_id
integer

Task type ID.

Example:

5

contract_id
integer

Related contract ID.

Example:

19

parent_task_id
integer

Parent task ID. When provided, the new task is created as a subtask.

Example:

1201

bug
boolean

Marks the task as a bug.

Example:

false

tags
string

Legacy raw tags field persisted on the task record.

Example:

"fiscal,api"

tagsSelect
string

Comma-separated tag IDs used to create task_tags relationships.

Example:

3813

checklist
string

Checklist payload persisted as a string.

Example:
received_form_id
integer

ID of the received form that originated the task.

Example:

77

task_followers
object[]

Explicit task followers.

task_tags
object[]

Tags to be attached to the task.

task_responsible
object[]

Additional responsible users. During creation, the API uses the user field to create the relationships.

custom_fields_value
object[]

Custom field values. Each item must include uuid and value.

Response

Task created successfully

id
integer
required

Internal task ID.

Example:

1532

task_id
integer
required

Public numeric task identifier.

Example:

1532

title
string
required
Example:

"Document task creation"

description
string | null
Example:

"Add request fields, response schema, and examples for POST /v2/tasks."

status
integer
Example:

0

due_date
string<date-time> | null
Example:

"2026-05-20T18:00:00.000Z"

delivery_date
string<date-time> | null
Example:

null

start_date
string<date-time> | null
Example:

"2026-05-19T12:00:00.000Z"

end_date
string<date-time> | null
Example:

null

created_at
string<date-time> | null
updated_at
string<date-time> | null
finished_at
string<date-time> | null
urgency
string | null
Example:

"Alta"

bug
boolean
Example:

false

estimated_time
string
Example:

"008:00"

worked_time
string
Example:

"000:00"

budget
string
Example:

"012:00"

type_id
integer | null
Example:

5

contract_id
integer | null
Example:

19

contract_service_id
integer | null
Example:

null

parent_task_id
integer | null
Example:

null

project_id
integer | null
Example:

8

project_name
string | null
Example:

"API Documentation"

column_id
integer | null
Example:

31

column_name
string | null
Example:

"Backlog"

client
object | null
responsibles
object[]
tags
object[]