The task endpoints work on the key owner's own work: items assigned to them in any project, plus personal tasks that aren't in a project. They're a good fit for personal assistants and daily digests, because a key only needs tasks scopes, not access to whole projects.
See what's on your plate
GET /v1/tasks/mine needs tasks:read. It sorts everything assigned to you into overdue, due_today, upcoming and no_due_date:
curl https://developers.playbookops.ai/v1/tasks/mine \
-H "Authorization: Bearer $PLAYBOOKOPS_API_KEY"
Add include_completed=true to include finished ones.
Personal tasks
With tasks:write:
| Call | What it does |
|---|---|
POST /v1/tasks | Creates a task outside any project. It's yours unless you pass assignee_id. |
PATCH /v1/tasks/TASK_ID | Updates a personal task, or a project item assigned to you. |
POST /v1/tasks/TASK_ID/complete | Completes it, or reopens it with {"completed": false}. |
curl -X POST https://developers.playbookops.ai/v1/tasks \
-H "Authorization: Bearer $PLAYBOOKOPS_API_KEY" -H "Content-Type: application/json" \
-d '{"title": "Renew the domain", "due_date": "2026-12-01", "priority": "urgent"}'
To change project items that aren't assigned to you, use the item endpoints with a projects:write key.
Reference
| Action | Endpoint | MCP tool |
|---|---|---|
| Your tasks | GET /v1/tasks/mine | my_tasks |
| Add a task | POST /v1/tasks | create_task |
| Update a task | PATCH /v1/tasks/{id} | update_task |
| Complete or reopen | POST /v1/tasks/{id}/complete | complete_task |
Every parameter is in the API reference.