REST API

The REST API lets your scripts and tools list, create, and update tasks. A token acts as you and can only do what you can do in the app.

Create a token

1. Go to Settings → API & AI agents → REST API and click Create token.
2. Enter a Name, choose the Workspace, and choose Access: Read or Read & write.
3. Click Create token and copy it. It starts with tk_ and isn't shown again.

Make a request

Copy the Base URL from the same page, then send the token in the Authorization header:

curl -H "Authorization: Bearer tk_…" "<base URL>/tasks?mine=1&due=today"

Endpoints

• GET /me: you and the token's workspace
• GET /boards: boards you can see
• GET /boards/:board/summary: lists and task counts
• GET /tasks?mine=1&due=today|week|overdue&board=…&q=…: find tasks
• GET /tasks/:task: one task, by key (TSK-12) or id
• POST /tasks: create a task with board, title, and optionally list, description, assignees, due_date, due_time, priority, labels
• PATCH /tasks/:task: change title, description, assignees, due_date, due_time, priority, labels, done, list, or board
• POST /tasks/:task/comments: add a comment with body
• POST /token/revoke: revoke the token making the request

Limits and errors

• Each token can make about 300 reads and 60 writes a minute. Over that, you get 429 with a Retry-After header.
• Errors come back as JSON: {"error": {"message": "…"}}.
• You can have up to 25 tokens.

Good to know

• A token works in one workspace.
• Tokens are stored hashed, so Taskeni can't show one again. If you lose it, revoke it and create a new one.
• To stop a token, click Revoke next to it. Anything using it stops working right away.
• The API is included on every plan.
• For AI assistants, use the MCP server instead. See Connect an AI assistant with MCP.