Skip to main content
PATCH
Update a board
Write access: a member/administrator with a write-enabled credential, or an authorized signed-in user. Edit board settings. Prefixes must be unique; changing one renames existing task identifiers while preserving task numbers and links. Send the current version to protect concurrent edits. A prefix change atomically renames existing task identifiers while preserving task numbers and UUID links. Existing task versions increase. Duplicate prefixes return 409 BOARD_PREFIX_TAKEN; stale versions conflict. Omitted fields remain unchanged. MCP clients can use update_board 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
version
integer
required
Required range: x <= 9007199254740991
name
string
Required string length: 1 - 100
description
string
Maximum string length: 10000
prefix
string
Pattern: ^[A-Z][A-Z0-9]{1,9}$

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.

board
object