ActivityWatch uses a REST API for all communication between aw-server and clients. Most applications should never use HTTP directly but should instead use the client libraries available. If no such library yet exists for a given language, this document is meant to provide enough specification to create one.
The API is currently under development, and is subject to change. It will be documented in better detail when first version has been frozen.
Part of the documentation might be outdated, you can get up-to-date API documentation in the API browser available from the web UI of your aw-server instance.
Our current security consists only of not allowing non-localhost connections, this is likely to be the case for quite a while.
Clients might in the future be able to have read-only or append-only access to buckets, providing additional security and preventing compromised clients from being able to cause a severe security breach. All clients will probably also encrypt data in transit.
This reference is highly incomplete. For an interactive view of the API, try out the API playground running on your local server at: http://localhost:5600/api/
The most common API used by ActivityWatch clients is the API providing read and append access buckets. Buckets are data containers used to group data together which shares some metadata (such as client type, hostname or location).
Will return 404 if bucket does not exist
Will return 304 if bucket already exists
The most common API used by ActivityWatch clients is the API providing read and append Events to buckets. Buckets are data containers used to group data together which shares some metadata (such as client type, hostname or location).
The heartbeat API is one of the most useful endpoints for writing watchers.
TODO: Add link to writing queries once that page is done