API
The app, the MCP server and the sync engine all run on the same operations. The REST API is one way in.
Reference
The interactive reference, generated from the API itself, lives at:
https://api.dododonedone.com/docs
Which way in
- To let an AI assistant work with your tasks, use the MCP server. It signs in with OAuth and needs no code.
- The REST API is what the web app talks to. It uses the same session as the app.
- Native clients use the sync protocol: plain JSON over HTTPS, documented, with offline writes.
Good to know
- IDs are UUIDv7 and are created by the client, so a task can exist before the server has seen it.
- When a workspace's trial or subscription has ended, writes answer 402 with SUBSCRIPTION_INACTIVE. Reads and export keep working.
- Sign-in and the MCP server are rate limited per IP and per connection; too many requests answer 429.
Coming later
Personal API keys and a public, versioned REST API for your own scripts and integrations. Until then, MCP is the supported way for tools outside the app.