One API, different clients

The web interface, GrigDesk driver and future clients use the same tracker API. An API-only distribution is also planned.

The contract is still in development. A published OpenAPI specification and verified request examples will accompany the release.

Token access

Personal API tokens have an expiration, read or write scope, and a set of projects. They remain within their owner’s current permissions and do not allow user administration.

The installation address must use HTTPS. Blocking a user revokes their sessions and tokens.

Changes and retries

The API is designed around operation identifiers and resource version checks. Retrying a request must not create another task; a version conflict must not silently overwrite someone else’s change.

After restoring a backup, clients must reconcile old actions against the new server history.

Events and files

The plan includes an event stream for interface updates, search, history, chunked uploads and resuming interrupted uploads. These operations also enforce permissions.

What you can prepare now

Identify the projects, client permissions and conflict-resolution scenarios your integration needs. Do not build against endpoints or schemas from the sample board: it uses no network API.

Related: poor connectivity, GrigDesk driver, project status.