Tasks and time blocks

GET/tasks

Tasks with their status and time blocks

List my tasks with their status (todo, scheduled, done) and their time blocks, including which calendars each block was written to. Done tasks are left out unless include_done is true.

MCP tool: list_tasks

Query parameters

curl "https://api.meetsynced.com/functions/v1/api/tasks" \
  -H "x-api-key: $SYNCED_API_KEY"

POST/tasks

Add a task

Add a task to my to-do list. It has no time on the calendar until schedule_task gives it a block.

MCP tool: create_task

JSON body

curl -X POST https://api.meetsynced.com/functions/v1/api/tasks \
  -H "x-api-key: $SYNCED_API_KEY" \
  -H "content-type: application/json" \
  -d '{"title":"…"}'

POST/tasks/capture

Add a task from a sentence and suggest times

Capture something the user needs time for and suggest when to do it. Pass the user's own words as `text` (e.g. 'write the Q1 deck by Friday, 2h') and Synced reads the title, length and due date, or pass the fields yourself. Creates the task and returns free times before its due date; nothing is put on the calendar. Show the suggestions, then call schedule_task with the chosen start. If `kind` comes back 'meeting', the text sounds like a meeting with people: ask who, and use find_meeting_time instead (the task is not created).

MCP tool: capture_task

JSON body

curl -X POST https://api.meetsynced.com/functions/v1/api/tasks/capture \
  -H "x-api-key: $SYNCED_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

POST/tasks/plan

Plan open tasks (dry run, then commit)

Lay out my open tasks in free time: earliest due date first, each before it's due, none overlapping each other or anything on my calendar, inside working hours. Without commit, nothing is written: it returns the plan and a plan_id. Show the plan to the user; when they agree, call again with commit: true and that plan_id. Committing twice is safe (the same plan never books twice), and any item whose time has since become busy is skipped and reported. At most 10 tasks per plan.

MCP tool: plan_tasks

JSON body

curl -X POST https://api.meetsynced.com/functions/v1/api/tasks/plan \
  -H "x-api-key: $SYNCED_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

PATCH/tasks/:id

Change a task

Change a task's title, notes, duration, due date or project. A new title is also applied to its upcoming calendar blocks.

MCP tool: update_task · :id is the task_id

JSON body

curl -X PATCH https://api.meetsynced.com/functions/v1/api/tasks/ID \
  -H "x-api-key: $SYNCED_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

DELETE/tasks/:id

Delete a task and its upcoming blocks

Delete a task and remove its upcoming time blocks from every calendar. Cannot be undone.

MCP tool: delete_task · :id is the task_id

curl -X DELETE "https://api.meetsynced.com/functions/v1/api/tasks/ID" \
  -H "x-api-key: $SYNCED_API_KEY"

POST/tasks/:id/complete

Mark a task done

Mark a task done. Its upcoming time blocks are removed from every calendar unless keep_future_blocks is true; past blocks stay as a record.

MCP tool: complete_task · :id is the task_id

JSON body

curl -X POST https://api.meetsynced.com/functions/v1/api/tasks/ID/complete \
  -H "x-api-key: $SYNCED_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

GET/tasks/:id/suggestions

Free times for a task

Suggest free times for a task, inside my working hours and avoiding busy time on all my calendars. The length is the task's duration. Returns start/end as ISO (pass one to schedule_task) plus local times in my timezone.

MCP tool: suggest_task_times · :id is the task_id

Query parameters

curl "https://api.meetsynced.com/functions/v1/api/tasks/ID/suggestions" \
  -H "x-api-key: $SYNCED_API_KEY"

POST/tasks/:id/schedule

Block time for a task

Block time for a task on my calendars. Writes one private, busy event to every account that allows time blocks (set in Settings → Calendars), or only to calendar_accounts when given. If start is omitted, nothing is scheduled: free-time suggestions are returned instead, so confirm one with the user and call again with its start. The result reports each calendar copy; failed copies can be retried with retry_task_block.

MCP tool: schedule_task · :id is the task_id

JSON body

curl -X POST https://api.meetsynced.com/functions/v1/api/tasks/ID/schedule \
  -H "x-api-key: $SYNCED_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

PATCH/task-blocks/:id

Move a time block

Move a task's time block on every calendar it was written to.

MCP tool: reschedule_task_block · :id is the block_id

JSON body

curl -X PATCH https://api.meetsynced.com/functions/v1/api/task-blocks/ID \
  -H "x-api-key: $SYNCED_API_KEY" \
  -H "content-type: application/json" \
  -d '{"start":"…"}'

DELETE/task-blocks/:id

Remove a time block

Remove a task's time block from every calendar. The task stays on the list; with no upcoming blocks left it goes back to 'todo'.

MCP tool: unschedule_task_block · :id is the block_id

curl -X DELETE "https://api.meetsynced.com/functions/v1/api/task-blocks/ID" \
  -H "x-api-key: $SYNCED_API_KEY"

POST/task-blocks/:id/retry

Retry calendar copies that failed

Write the calendar copies of a time block that failed earlier (schedule_task reports failures per account).

MCP tool: retry_task_block · :id is the block_id

curl -X POST https://api.meetsynced.com/functions/v1/api/task-blocks/ID/retry \
  -H "x-api-key: $SYNCED_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'