Skip to main content
POST
Create a task
Write access: a member/administrator with a write-enabled credential, or an authorized signed-in user. Create a task with optional Markdown description and acceptance criteria, type task or bug, a fixed status, assignee, priority, start date and due date. Type defaults to task and status to todo. Reuse the Idempotency-Key header on retries. Creation requires title and defaults type to task, status to todo, priority to none, assignee and dates to null, and Markdown fields to empty. Active human assignees only. Mentions and assignments respect in-app notification preferences. MCP clients can use create_task for this operation. Request conventions · API keys · MCP connections

Authorizations

Authorization
string
header
required

Personal or team Mill REST API key

Headers

Origin
string<uri>

The exact configured Mill UI origin. Required for browser mutations carrying session cookies.

Idempotency-Key
string

Reuse the same key and exact request bytes for retries of one logical mutation; different content conflicts.

Required string length: 8 - 128
Pattern: ^[A-Za-z0-9._:-]+$

Path Parameters

boardId
string<uuid>
required

The boardId from the corresponding list, record or authorization response.

Body

application/json
title
string
required
Required string length: 1 - 300
type
enum<string>
Available options:
task,
bug
description
string
Maximum string length: 100000
acceptanceCriteria
string
Maximum string length: 100000
assigneeId
string<uuid> | null
Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$
priority
enum<string>
Available options:
none,
low,
medium,
high,
urgent
status
enum<string>
Available options:
backlog,
todo,
in_progress,
in_review,
done,
wont_do
startDate
string<date> | null
Pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$
dueDate
string<date> | null
Pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$

Response

Successful response. Examples are illustrative; field values vary by record.

Illustrative response shape. Fields can be absent in alternate successful flows; see the operation description and example.

task
object