Skip to main content
POST
Assign and Update Project To-dos
Both actions require project_todos:write, a claimed account, and employer access to the job. Both fan out only to an explicit audience, and broad audiences require a fresh preflightReceipt for the exact request.

assign

Assigns the item’s current version to the stated audience. Recipients who already hold this operation’s assignment are skipped, so a same-key retry converges instead of duplicating obligations. A new assignment supersedes that person’s stale open copy of the same item; submitted work stays reviewable.
string
required
assign
string
required
string
required
string
required
string
required
No default. FUTURE and ACTIVE_AND_FUTURE also turn on future-hire auto-assignment for the item.
string[]
SELECTED only; validated strictly.
string
Required for broad audiences; bound to the item’s current version, so a version published between preflight and assign invalidates it.
The response mirrors create_item: audience echo, fanOut, and masked recipients.

update_item

Publishes a new immutable version of the definition. With assign, the new version is issued to the stated audience in the same transaction, superseding stale open assignments; without it, nothing is reissued.
string
required
update_item
string
required
string
required
string
required
object
required
The complete new definition.
object
Optional reissue: audience, selectedContractIds, and preflightReceipt for broad audiences — bound to the item and the exact new definition.
Every update_item call publishes another version — retries are not convergent. If a call’s outcome is uncertain, read the item before sending again instead of blind-retrying.