Plan · Home & search

The calling user's tasks

Your tasks, the same as GET /v1/plan/tasks/?owner=me plus the scope choice. Needs a person: an agent or organization key gets 403 insufficient_scope, never an empty list; a personal API key works.

curl -sS "https://api.dailybot.com/v1/plan/me/tasks/?scope=involved&state=open" \
  -H "Authorization: Bearer $DAILYBOT_TOKEN"

dailybot plan tasks mine --scope involved --json

{
  "count": 1,
  "next": null,
  "previous": null,
  "results": [
    {
      "uuid": "00000000-0000-4000-8000-000000000005",
      "key": "ENG-142",
      "title": "Ship the delta feed",
      "description": null,
      "board": "00000000-0000-4000-8000-000000000002",
      "state": {
        "uuid": "00000000-0000-4000-8000-000000000003",
        "name": "In Progress",
        "category": "in_progress",
        "position": 2
      },
      "priority": 2,
      "estimate": 3,
      "owner": {
        "uuid": "00000000-0000-4000-8000-00000000000c",
        "name": "Ada L."
      },
      "executor": null,
      "participant_count": 1,
      "start_date": "2026-09-28",
      "due_date": "2026-10-15",
      "milestone": null,
      "parent_task": null,
      "subtask_count": 1,
      "subtask_done_count": 1,
      "attachment_count": 1,
      "open_blocker_count": 1,
      "labels": [],
      "rank": "aU",
      "blocked": false,
      "blocked_since": null,
      "completed_at": null,
      "is_archived": false,
      "subscribed": true,
      "version": 7,
      "created_by": {
        "kind": "user",
        "uuid": "00000000-0000-4000-8000-00000000000c",
        "name": "Ada L."
      },
      "created_at": "2026-09-25T10:14:02Z",
      "updated_at": "2026-09-25T10:14:02Z"
    }
  ]
}

• Scope: `tasks:read`.
• Rate limit: 120 reads 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`.

Personal task tab counts

Caller-scoped counts for owned, participating, involved, and overdue work. The four top-level integers are population totals across every lifecycle: owned counts every task assigned to the caller whether it is open, done or canceled. overdue is the exception and is owned-only, already excluding archived and terminal work. by_scope carries the status-qualified numbers, so a badge can say "N open" without a second request. open is decided by the state CATEGORY, exactly as ?state=open decides it; overdue means open AND past due; blocked uses the one live-blocker predicate. Every number is computed in the same single aggregate over the same visibility root. by_scope.<scope>.total equals the top-level integer of the same name by construction.

curl -sS "https://api.dailybot.com/v1/plan/me/tasks/counts/" \
  -H "Authorization: Bearer $DAILYBOT_TOKEN"

dailybot plan tasks counts

{
  "owned": 1,
  "participating": 1,
  "involved": 1,
  "overdue": 1,
  "by_scope": {}
}

• Scope: `tasks:read`.
• Rate limit: 120 reads 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`.

Recently visited boards for the caller

Boards you opened recently, newest first, as recorded by POST /v1/plan/boards/{board_id}/visit/. Hidden, archived and other organizations' boards are omitted rather than raised. Needs a person (an agent or organization key gets 403; a personal API key works).

curl -sS "https://api.dailybot.com/v1/plan/me/recents/" \
  -H "Authorization: Bearer $DAILYBOT_TOKEN"

{
  "count": 1,
  "limit": 1,
  "results": []
}

• Scope: `tasks:read`.
• Rate limit: 120 reads 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`.

Notification-worthy task events for the caller

Your inbox: task events worth your attention, newest first, as a page. mentioned=true keeps only the events where someone mentioned you; type keeps one event type. Both combine, and count and paging are exact, so there are no empty pages.

curl -sS "https://api.dailybot.com/v1/plan/inbox/" \
  -H "Authorization: Bearer $DAILYBOT_TOKEN"

dailybot plan tasks inbox --json

{
  "count": 1,
  "next": null,
  "previous": null,
  "results": [
    {
      "uuid": "00000000-0000-4000-8000-00000000000f",
      "type": "task.moved",
      "actor": {},
      "created_at": "example",
      "task": {},
      "payload": {},
      "changes": []
    }
  ]
}

• Scope: `tasks:read`.
• Rate limit: 120 reads 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`.

Unread inbox count for the caller

How many inbox items you have not read yet, for a badge. It takes the same filters as the inbox list, so each tab's badge counts exactly that tab's rows: mentioned=true for Mentions, type=task.owner_changed for Assigned. With no parameters it counts the whole inbox. Cheaper than listing the inbox.

curl -sS "https://api.dailybot.com/v1/plan/inbox/unread-count/" \
  -H "Authorization: Bearer $DAILYBOT_TOKEN"

dailybot plan tasks inbox-unread

{
  "unread_count": 3
}

• Scope: `tasks:read`.
• Rate limit: 120 reads 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`.

Org activity feed for Plan Home

Paginated events you may open, enriched with task cards and resolved changes[{field, from, to}] for display. Tasks you cannot see are omitted even when their board is visible.

Only the parameters listed here are accepted: any other query parameter is 400 invalid_filter_value.

curl -sS "https://api.dailybot.com/v1/plan/activity/" \
  -H "X-API-KEY: $DAILYBOT_API_KEY"

dailybot plan tasks activity --last-week --json
dailybot plan tasks activity --board 00000000-0000-4000-8000-000000000002 --since 2026-09-20T00:00:00Z --json

• Scope: `tasks:read`.
• Rate limit: 120 reads 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.

Read the caller's activity read cursor

Your activity read cursor: the moment up to which you have read the activity feed. It is null until you set it.

curl -sS "https://api.dailybot.com/v1/plan/me/activity-cursor/" \
  -H "Authorization: Bearer $DAILYBOT_TOKEN"

dailybot plan tasks cursor

{
  "last_seen_at": null
}

• Scope: `tasks:read`.
• Rate limit: 120 reads 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`.

List organization labels

The organization's label taxonomy, shared with forms and check-ins. Prefer this endpoint for settings screens; the board-scoped list is the same taxonomy behind a board access check.

curl -sS "https://api.dailybot.com/v1/plan/labels/" \
  -H "Authorization: Bearer $DAILYBOT_TOKEN"

{
  "count": 1,
  "next": null,
  "previous": null,
  "results": [
    {
      "uuid": "00000000-0000-4000-8000-00000000000b",
      "name": "backend",
      "color": "#2563eb"
    }
  ]
}

• Scope: `tasks:read`.
• Rate limit: 120 reads 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`.

Whether Plan is available here, and the plan ceilings

Whether Plan is available to your organization, and its plan ceilings. It is the one Plan endpoint that never answers 402, so call it before deciding whether to show the product.

enabled is the same check every other endpoint applies. reason is null when enabled; otherwise rollout (your organization is not enabled for the Beta yet) or usage (an admin turned Plan off). boards and projects report {used, limit}, even when disabled; limit is null when the plan has no cap. The free plan includes up to 3 boards and 1 project. used counts live rows only, so archiving frees a slot, and used > limit can happen on grandfathered plans.

A guest gets 403 guest_not_allowed here, not 200 with enabled: false, and never sees plan ceilings.

curl -sS "https://api.dailybot.com/v1/plan/entitlements/" \
  -H "X-API-KEY: $DAILYBOT_API_KEY"

dailybot plan tasks entitlements

{
  "enabled": false,
  "reason": null,
  "boards": {},
  "projects": {},
  "labels": {}
}

• Scope: `tasks:read`.
• Rate limit: 120 reads 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.

The scheduled work over a window, with its dependency edges and goal bands

The same filtered set as the task list, asked a scheduling question. rows are the cards that OVERLAP the window; unscheduled counts the matching cards with no dates at all; dependencies carries only edges whose both ends are in rows, because an arrow to a row the reader cannot see is a line to nowhere on the screen and a disclosure off it. Window selection (first match wins): - from + to (ISO dates) — explicit range; from may be in the past (e.g. today−7 … today+21). Aliases: window_from / window_to. - window_days — forward helper: today through today+N (inclusive span). - omitted — default forward window of 14 days from today (with a board filter).

curl -sS "https://api.dailybot.com/v1/plan/timeline/?board=ENG&from=2026-09-18&to=2026-10-16" \
  -H "X-API-KEY: $DAILYBOT_API_KEY"

dailybot plan tasks timeline --today

{
  "window": {},
  "bands": [],
  "rows": [],
  "dependencies": [],
  "unscheduled": 1,
  "truncated": false
}

• Scope: `tasks:read`.
• Rate limit: 120 reads 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.

Search tasks and containers visible to the caller

Search tasks (title, key, description) and, with types, projects, boards and goals you can see.

Matching is case-insensitive substring search, not full-text ranking. score is a coarse ordering aid between 0.6 and 1.0 (exact key 1.0, title or name hit 0.9 / 0.85, description hit 0.6), not calibrated relevance, and snippet is a window around the first match. The response repeats this in approximation. Hidden tasks and private boards never appear.

curl -sS "https://api.dailybot.com/v1/plan/search/?q=delta&types=task,board" \
  -H "X-API-KEY: $DAILYBOT_API_KEY"

dailybot plan tasks search -q "delta" --json

{
  "q": "delta",
  "limit": 1,
  "approximation": "substring",
  "results": []
}

• Scope: `tasks:read`.
• Rate limit: 120 reads 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.

The home screen in one request (HomePulse), or a board-health aggregate (TaskPulse)

Two modes, chosen by the presence of group_by.

HomePulse (no group_by): the Plan home in one request — generated_at, integer counts, your my_preview, board, goal and timeline teasers, agent_summary, and the optional include bands. The population is stated as scope: "viewer_visible": every live, non-terminal task you can see — not the whole organization. Each tile names the query that reproduces it: open → ?state=open, overdue → ?due_before=<today>&state=open, blocked → ?blocked=true&state=open.

TaskPulse (with group_by, e.g. group_by=state): a board-health aggregate with totals, throughput and cycle time. Counts are integers only and there is no per-person breakdown. Answers If-None-Match with 304.

curl -sS "https://api.dailybot.com/v1/plan/pulse/?include=projects,attention,activity,goal_progress" \
  -H "X-API-KEY: $DAILYBOT_API_KEY"

dailybot plan tasks status --json

• Scope: `tasks:read`.
• Rate limit: 120 reads 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.

Your pinned boards and saved views

Every pin you own, in rank order (1 is the top). A pin whose target you can no longer see (an archived or hidden board, or a saved view that is gone or no longer shared) is omitted rather than raised. The list uses the standard list envelope but is never paged: next and previous are always null, and it holds up to 50 pins. Needs a person: agent and organization keys are refused; a personal API key works.

curl -sS "https://api.dailybot.com/v1/plan/me/favorites/" \
  -H "Authorization: Bearer $DAILYBOT_TOKEN"

dailybot plan tasks favorites --json

{
  "count": 1,
  "next": null,
  "previous": null,
  "results": [
    {
      "uuid": "00000000-0000-4000-8000-000000000012",
      "target_type": "board",
      "target_uuid": "00000000-0000-4000-8000-000000000012",
      "rank": "aU",
      "created_at": "2026-09-25T10:14:02Z"
    }
  ]
}

• Scope: `tasks:read`.
• Rate limit: 120 reads 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`.