Get It Done

Move an entry between sections

PATCH/v1/daily-plan/entries/{entry_id}

Moves a board entry to the other section of the same date, mirroring the in-app move: subtask entries of a parent move along, a task already present in the target section answers 400 `validation_failed`, and the move RE-CREATES the entry — the returned entry carries a NEW id. Sections are the only movement the board models (no positional reorder exists).

Required scopes

tasks:write

Availability

All plans

Quota cost

1 API call

Idempotency

Not applicable

Request

Path parameters

Field	Type	Description
`entry_id`required	string

Request body

Field	Type	Description
`section`required	"TODO" \| "PROGRESS"	Daily-board section: `TODO` = the plan list, `PROGRESS` = the in-progress list.

▸ Raw request schema

{
  "type": "object",
  "properties": {
    "section": {
      "$ref": "#/components/schemas/DailySection"
    }
  },
  "required": [
    "section"
  ],
  "description": "The target section."
}

Response 200

The entry in its new section (new id).

Fields

Field	Type	Description
`id`required	string	Board-entry id. NOTE: moving an entry between sections re-creates it (mirroring the in-app move), so the id CHANGES on move.
`section`required	"TODO" \| "PROGRESS"	Daily-board section: `TODO` = the plan list, `PROGRESS` = the in-progress list.
`task_id`required	string	The planned task's short id.e.g. `T-123`
`title`required	string	The planned task's current title.
`status`required	"TODO" \| "IN_PROGRESS" \| "IN_REVIEW" \| "COMPLETED" \| "BLOCKED"	Task workflow status.
`created_at`required	string (date-time)	When the task was placed on this section, ISO-8601 UTC. Entries within a section are ordered by this (oldest first) — there is no free positional reorder.

▸ Raw response schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Board-entry id. NOTE: moving an entry between sections re-creates it (mirroring the in-app move), so the id CHANGES on move."
    },
    "section": {
      "$ref": "#/components/schemas/DailySection"
    },
    "task_id": {
      "type": "string",
      "description": "The planned task's short id.",
      "example": "T-123"
    },
    "title": {
      "type": "string",
      "description": "The planned task's current title."
    },
    "status": {
      "description": "The planned task's current workflow status.",
      "$ref": "#/components/schemas/TaskStatus"
    },
    "created_at": {
      "type": "string",
      "format": "date-time",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
      "description": "When the task was placed on this section, ISO-8601 UTC. Entries within a section are ordered by this (oldest first) — there is no free positional reorder."
    }
  },
  "required": [
    "id",
    "section",
    "task_id",
    "title",
    "status",
    "created_at"
  ],
  "additionalProperties": false,
  "description": "One task pinned onto one daily-board section."
}

Example request

curl

curl -X PATCH https://app.nowgetitdone.com/v1/daily-plan/entries/id_123 \
  -H "Authorization: Bearer gid_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "section": "TODO"
  }'