Snooze task
Moves a task's target (due_at) — the same move as PATCH { target_at }
(2026-10-12, spec §6: there is no snooze state). It stops at the task's
deadline while that deadline is still ahead (spec §8.2): the response's
capped_at_deadline is true when it did. Once the deadline has passed
the cap is off and any target can be picked (2026-10-12).
allow_past_deadline and cap_at_deadline are accepted from
old clients and change nothing. Two populations refuse it with a 400,
because neither has a due date to move: reminders (§6), which stay in
their time slot until completed, and quotas (§5), which are counted
within a period rather than due on a day. The bulk snooze sweep skips
both instead of failing.
Authorizations
API token created via POST /api/tokens or the db:create-token CLI command
Request Body
Responses
Snoozed task