The desktop app uses an API for account-backed data and synchronization, but there is not yet a stable, supported API for third-party applications. Interfaces are changing alongside the desktop alpha.

Exploring the implementation

The current source repository is the place to inspect the implementation. Treat the code as development material, not a versioned integration contract: routes, data formats and authentication requirements may change.

There is no public API-key issuance flow advertised here. Signing into this website provides access to website account settings; it does not by itself authorize requests to the task API or grant access to desktop task data.

Planning an integration

Before depending on an endpoint, describe what your integration needs to read or change and how you expect it to handle synchronization. The Project page explains how to share feedback and follow development.

Keep credentials and real workspace data out of public reports. Small examples with invented data are enough to explain most integration needs.