Skip to main content
The Project To-dos API reads and edits the same continuous list shown in a job’s employer Project To-dos tab and in each AI trainer’s manage-job view.

​
Endpoints

​
Manage actions

POST /project-todos/manage dispatches on action:

​
Authorization

List, export, and quiz reads require project_todos:read. Every manage action requires project_todos:write and a claimed account, plus employer access to the job (or, for worker_transition, ownership of the contract). The account must also have the default-off project_todos_integrations agent-surface family enabled. Scope failures return 403 with the missing resource named in details; a disabled family returns 403 with details.reason = "AGENT_SURFACE_DISABLED".

​
Write safety

  • audience is required on every fan-out — omission is a 400, never a broadcast. See the concept page for audience semantics.
  • Broad audiences require a preflightReceipt from a matching preflight call.
  • Every mutating action requires idempotencyKey (8–200 characters). Creation keys are bound to the complete request.
  • Item creation, version publication, and assignment fan-out commit in one transaction.

​
Common errors

Use the machine-readable OpenAPI document for complete schemas.