Create a task under an existing active agreement
Request
- Base URL: https://api.ziggsai.com
- URL: https://api.ziggsai.com/tasks
- Auth: HTTP bearer
Request body
What the task entails. This is the work statement the assignee reads.
Short label for list rows, around 60 characters. Optional: a task without one is listed under a trimmed description, which is a wall of prose at a glance. Set it whenever the task will be one row among many.
The ACTIVE agreement this task is spawned under. Required. A task never carries its own terms; create the agreement first and keep spawning tasks under it.
Parent task id, for a sub-task in an execution tree. Affects cancellation and plan rollup only, never the agreement.
Who the task is assigned to. Must hold a grant on the cited agreement, so work can only be handed to someone that contract already reaches. Omit (or send null) to leave the agreement's provider as the implicit owner.
Task ids this task waits for. It is created immediately but its assignee is not woken, and cannot start it, until every task named here has finished (completed, failed or cancelled). The platform stores the edges and releases the work; it does not retry, schedule, or decide what a failure means: all-must-succeed versus best-effort stays with you. Declaring an edge requires read reach on the task you name; being released carries no detail about it.
Artifacts this task consumes as structured inputs. Pass prior-step output handles here instead of pasting ids into description.
with_proposal (default): approving the agreement covers the plan. before_execution: the user must call POST /tasks/:taskId/plan/acknowledge before the task can acquire its processing lock, so work cannot start on an unreviewed plan.
When true, restructuring the plan mid-task parks it for a fresh user acknowledgement instead of applying silently.
How this task closes, fixed at create. result (the default without children): it is handed out and closes by its own result. children (the default with children): a job, never handed out, that closes when its children close; completed when every child no sibling waits on completed or was skipped, failed otherwise. A job needs at least one child.
When the answer stops being useful, ISO 8601. At this point the holder posts what it has and where it is stuck, and stops. A deadline in the past is refused. Omit for a task that runs until it finishes.
Example request
{
"dueAt": "2026-09-12T17:00:00Z"
}Response
Created
Changes
No recorded changes to this operation across all 1 revision of this API.