Build your own client
Every OpenTodo server speaks the same HTTP API the official apps use.
Three ways in
REST API
Tasks, projects, notes, labels and everything else over
/api/v1, with JSON in and out. Enough for a script, a bot or a client that works online.Sync protocol
The operation log the official apps use: send changes made offline, or keep a full copy and merge everyone’s changes.
Webhooks and MCP
Signed events when tasks and projects change, and MCP for AI assistants.
Start here
Sign in with an API token
The person creates a token on their server and gives it to your client. There is no sign-in flow for other apps.
- On GitHub, not in a release yet
Build your own OpenTodo client
The guide: which way in to choose, tokens, device ids, the outbox and rate limits.
- On GitHub, not in a release yet
OpenAPI description
Every route and field, for generating types. From the next release, every server also serves it at
/api/v1/openapi.json.
Clients to learn from
Obsidian plugin
Sends changes through the sync protocol and keeps them in an outbox while offline.
Community clients
None yet.
Built one? Add the topic opentodo-client to its repository and open a pull request adding it to community-clients.json. Listed clients are marked not vetted by OpenTodo.