Plan · Tasks

Create a task on this board (alias of `POST /v1/plan/tasks/`)

Same create semantics as POST /v1/plan/tasks/ with the board taken from the path (board in the body is optional and overridden). Idempotency-Key is optional and recommended.

curl -sS -X POST "https://api.dailybot.com/v1/plan/boards/00000000-0000-4000-8000-000000000002/tasks/" \
  -H "X-API-KEY: $DAILYBOT_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Ship the delta feed",
    "priority": 2
  }'

dailybot plan task create -t "Ship the delta feed" -b 00000000-0000-4000-8000-000000000002

• Scope: `tasks:write`.
• Rate limit: 60 writes per minute per actor.
• Works with a login session, a CLI user token, a personal API key, or an agent or organization key. A personal key sees what its person sees; an agent or organization key acts as a system actor and sees organization-visible boards only.

Create a task

The key (ENG-143) is allocated from the board's counter and never reused, even after archive.

When owner is set, that person must already be able to see the board; otherwise the call is refused with 400 participant_cannot_access_board and nothing is written.

Placement is relative: after or before names a visible task in the target column (at most one of them); omit both to append at the end. Raw rank is never accepted.

curl -sS -X POST "https://api.dailybot.com/v1/plan/tasks/" \
  -H "X-API-KEY: $DAILYBOT_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "board": "00000000-0000-4000-8000-000000000002",
    "title": "Ship the delta feed",
    "priority": 2,
    "due_date": "2026-10-15"
  }'

dailybot plan task create -t "Ship the delta feed" -b 00000000-0000-4000-8000-000000000002 --owner me --priority 2

• Scope: `tasks:write`.
• Rate limit: 60 writes per minute per actor.
• Works with a login session, a CLI user token, a personal API key, or an agent or organization key. A personal key sees what its person sees; an agent or organization key acts as a system actor and sees organization-visible boards only.

Create, or apply one operation to, up to 100 tasks

Registered BEFORE the {task_id} detail route, or bulk parses as an identifier. Atomicity is per item, not per batch: the response reports each item separately and the HTTP status describes whether the batch was accepted, not whether every item succeeded. Idempotency-Key is required — a bulk move that half-applies twice is a corrupted board. The restore operation is the batch form of POST .../tasks/{task_id}/restore/ and obeys the same rules.

curl -sS -X POST "https://api.dailybot.com/v1/plan/tasks/bulk/" \
  -H "X-API-KEY: $DAILYBOT_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "operation": "create",
    "board": "00000000-0000-4000-8000-000000000002",
    "items": [
      {
        "title": "Write the migration guide",
        "external_id": "row-1"
      },
      {
        "title": "Record the demo",
        "external_id": "row-2"
      }
    ]
  }'

dailybot plan task bulk --operation create --board 00000000-0000-4000-8000-000000000002 -f tasks.json --dry-run
dailybot plan task bulk --operation create --board 00000000-0000-4000-8000-000000000002 -f tasks.json

{
  "succeeded": 1,
  "failed": 1,
  "results": [
    {
      "task": "ENG-142",
      "status": "ok",
      "version": 8
    },
    {
      "task": "ENG-9",
      "status": "error",
      "code": "version_conflict",
      "detail": "This task changed since you loaded it.",
      "extra": {
        "current_version": 4
      }
    }
  ]
}

• Scope: `tasks:write`.
• Rate limit: 30 bulk calls per minute per actor.
• Works with a login session, a CLI user token, a personal API key, or an agent or organization key. A personal key sees what its person sees; an agent or organization key acts as a system actor and sees organization-visible boards only.

Archive a task and its sub-tasks

Archiving nulls the task's rank, so it leaves every board ordering without leaving the table. Relations and participants are kept.

curl -sS -X POST "https://api.dailybot.com/v1/plan/tasks/ENG-142/archive/" \
  -H "X-API-KEY: $DAILYBOT_API_KEY"

dailybot plan task archive ENG-142 --dry-run
dailybot plan task archive ENG-142 --yes

• Scope: `tasks:write`.
• Rate limit: 60 writes per minute per actor.
• Works with a login session, a CLI user token, a personal API key, or an agent or organization key. A personal key sees what its person sees; an agent or organization key acts as a system actor and sees organization-visible boards only.

Duplicate a task on the same board

Creates a new task in the same column. Default include copies title, description, and labels. Emits task.created.

curl -sS -X POST "https://api.dailybot.com/v1/plan/tasks/ENG-142/duplicate/" \
  -H "X-API-KEY: $DAILYBOT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "include": [
      "title",
      "description",
      "labels"
    ]
  }'

dailybot plan task duplicate ENG-142 --include title --include description

• Scope: `tasks:write`.
• Rate limit: 60 writes per minute per actor.
• Works with a login session, a CLI user token, a personal API key, or an agent or organization key. A personal key sees what its person sees; an agent or organization key acts as a system actor and sees organization-visible boards only.

Move a task to another board

Body requires board (target board uuid). Target column resolution: explicit state, or state_map from source column uuid → target column uuid, or same category on the target board. Emits task.moved (with from_board_uuid when crossing boards). Invalid mappings return 400 move_board_state_invalid.

curl -sS -X POST "https://api.dailybot.com/v1/plan/tasks/ENG-142/move-board/" \
  -H "X-API-KEY: $DAILYBOT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "board": "00000000-0000-4000-8000-000000000012"
  }'

dailybot plan task move ENG-142 --board 00000000-0000-4000-8000-000000000012

• Scope: `tasks:write`.
• Rate limit: 60 writes per minute per actor.
• Works with a login session, a CLI user token, a personal API key, or an agent or organization key. A personal key sees what its person sees; an agent or organization key acts as a system actor and sees organization-visible boards only.

Move a task to a state and a position, relatively

The only way to change a task's state. The position is a neighbour, not a number, so two people dragging the same card at once both produce a valid order. At most one of after / before may be set; both null appends to the end of the column. One write, one task.moved event. Send If-Match (or version) to refuse a stale move.

curl -sS -X POST "https://api.dailybot.com/v1/plan/tasks/ENG-142/move/" \
  -H "X-API-KEY: $DAILYBOT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "state": "00000000-0000-4000-8000-000000000004",
    "after": null,
    "before": null
  }'

dailybot plan task move ENG-142 --state done

• Scope: `tasks:write`.
• Rate limit: 60 writes per minute per actor.
• Works with a login session, a CLI user token, a personal API key, or an agent or organization key. A personal key sees what its person sees; an agent or organization key acts as a system actor and sees organization-visible boards only.

Link two tasks

Links this task to another one. Send relation_type (blocks, relates_to or duplicates) and target_task, a task uuid or a key like ENG-142; a task you cannot see is 404. kind and target are deprecated aliases of those two fields: sending an alias and its field with different values is 400. A link that already exists or would create a cycle is 409.

curl -sS -X POST "https://api.dailybot.com/v1/plan/tasks/ENG-142/relations/" \
  -H "X-API-KEY: $DAILYBOT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "relation_type": "blocks",
    "target_task": "ENG-150"
  }'

dailybot plan task link ENG-142 ENG-150 --type blocks

• Scope: `tasks:write`.
• Rate limit: 60 writes per minute per actor.
• Works with a login session, a CLI user token, a personal API key, or an agent or organization key. A personal key sees what its person sees; an agent or organization key acts as a system actor and sees organization-visible boards only.

Attach, detach or replace a task's labels

Labels are the organization-wide taxonomy shared with forms and check-ins; there is no plan-only label vocabulary. At most 50 labels per task.

curl -sS -X POST "https://api.dailybot.com/v1/plan/tasks/ENG-142/labels/batch/" \
  -H "X-API-KEY: $DAILYBOT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "add",
    "label_uuids": [
      "00000000-0000-4000-8000-00000000000b"
    ]
  }'

dailybot plan task labels ENG-142 --mode add --label 00000000-0000-4000-8000-00000000000b

{
  "labels": [
    {
      "uuid": "00000000-0000-4000-8000-00000000000b",
      "name": "backend",
      "color": "#2563eb"
    }
  ]
}

• Scope: `tasks:write`.
• Rate limit: 60 writes per minute per actor.
• Works with a login session, a CLI user token, a personal API key, or an agent or organization key. A personal key sees what its person sees; an agent or organization key acts as a system actor and sees organization-visible boards only.

Subscribe to task notifications (watcher role)

The only way to set the task's subscribed field (sending subscribed in a task PATCH is 400). Returns {"subscribed": true}, so no re-read is needed.

curl -sS -X POST "https://api.dailybot.com/v1/plan/tasks/ENG-142/subscription/" \
  -H "Authorization: Bearer $DAILYBOT_TOKEN"

dailybot plan task watch ENG-142

{
  "subscribed": true
}

• Scope: `tasks:write`.
• Rate limit: 60 writes per minute per actor.
• Needs a person: call it with a login session, a CLI user token or a personal API key. An agent or organization key gets `403 insufficient_scope`.

Restore an archived task

The mirror of archive: same scope, same credentials, same idempotency. The task returns at the end of its column, because its old neighbours are gone. Restoring a live task is a no-op 200.

curl -sS -X POST "https://api.dailybot.com/v1/plan/tasks/ENG-142/restore/" \
  -H "X-API-KEY: $DAILYBOT_API_KEY"

dailybot plan task restore ENG-142

• Scope: `tasks:write`.
• Rate limit: 60 writes per minute per actor.
• Works with a login session, a CLI user token, a personal API key, or an agent or organization key. A personal key sees what its person sees; an agent or organization key acts as a system actor and sees organization-visible boards only.

Put someone on this card

Adds a participant or watcher. Adding someone already on the card returns 200 with the existing row. Adding or removing a participant emits task.participant_added with actor_is_self, so "someone added me" and "I joined" can be told apart. A watcher change emits nothing: following a task is a private preference. Muting (is_muted) keeps the person on the card.

curl -sS -X POST "https://api.dailybot.com/v1/plan/tasks/ENG-142/participants/" \
  -H "Authorization: Bearer $DAILYBOT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "user_uuid": "00000000-0000-4000-8000-00000000000c",
    "role": "participant"
  }'

dailybot plan task participants add ENG-142 --user 00000000-0000-4000-8000-00000000000c --role participant
dailybot plan task mute ENG-142
dailybot plan task unmute ENG-142

• Scope: `tasks:write`.
• Rate limit: 60 writes per minute per actor.
• Needs a person: call it with a login session, a CLI user token or a personal API key. An agent or organization key gets `403 insufficient_scope`.