.svg){kind=small}
.svg){kind=small}
DEVELOPER DOCUMENTATION
Assign and Update Project To-dos
Reissue the current version to a stated audience, or publish a new immutable version with an optional reissue.
/api/public/v1/project-todos/manageBoth 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
Section titled “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.
actionstringbodyrequiredassignidempotencyKeystringbodyrequiredjobIdstringbodyrequireditemIdstringbodyrequiredaudiencestringbodyrequiredNo default. FUTURE and ACTIVE_AND_FUTURE also turn on future-hire auto-assignment for the item.
selectedContractIdsstring[]bodySELECTED only; validated strictly.preflightReceiptstringbodyRequired 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
Section titled “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.
actionstringbodyrequiredupdate_itemidempotencyKeystringbodyrequiredjobIdstringbodyrequireditemIdstringbodyrequiredversionobjectbodyrequiredassignobjectbodyOptional reissue: audience, selectedContractIds, and preflightReceipt for broad audiences — bound to the item and the exact new definition.