Skip to content

Create a Task

Create a task with the right title, ownership, and optional planning context from the start.

Best for Human member and Automation developer Updated April 3, 2026
API In this interface
4 steps Steps
1 examples Examples
Use this path when

Create a task over REST with the fields your workflow already knows and can justify.

What you'll finish here
  • Use the right creation surface.
  • Fill required fields first.
  • Attach optional planning and ownership fields correctly.

Where this happens

LabelValueNotes
EndpointPOST /api/v1/workspaces/{workspaceId}/tasksCreates one task.

Same Task, Other Interfaces

Use the version that matches where you are working now. The subject matter stays the same; the delivery changes by surface.

Do the work

  1. 1. Send a bearer token with `tasks.write`.
  2. 2. Include at least `title` and `teamId` in the JSON body.
  3. 3. Add optional fields only when they are meaningful now: `description`, `projectId`, `milestoneId`, `assigneeId`, `deadlineAt`, `priority`, `status`, and `tags`.
  4. 4. Read the creation result and keep the new task id for the next step in the workflow.

Create a task over REST

bash
curl -X POST http://localhost:5173/api/v1/workspaces/ws_123/tasks   -H 'authorization: Bearer access_token_here'   -H 'content-type: application/json'   -d '{"title":"Ship public docs","teamId":"team_123","priority":"high","status":"planned"}'

Keep Going in Task Workflows

Stay in the same interface and move to the next closest task in this topic when needed.

Nearby Guides

These guides stay close to the current workflow so you can keep moving without restarting discovery.