Files
TimeTracker/docs/api
Dries Peeters eb2f5c6afa fix(apps): harden desktop and mobile server connectivity
Desktop (Electron):
- Add two-step first-run wizard: test TimeTracker via GET /api/v1/info, then log in with API token
- Replace bogus token check with validateSession (users/me, fallback to timer/status for narrow scopes)
- Normalize base URLs; classify TLS/DNS/timeout errors; periodic 401 forces re-login
- Settings save/test use public + authenticated checks; prebuild/prestart and npm test

Server:
- Exempt /api/v1/info, /api/v1/health, and POST /api/v1/auth/login from HTML setup redirect
- Include setup_required on GET /api/v1/info for unfinished installs

Mobile (Flutter):
- Validate saved token against new server URL before persisting settings change
- Remove unused lib/core/config.dart; point BUILD_CONFIGURATION at app_config.dart

Docs: DESKTOP_SETTINGS, desktop README, mobile-desktop-apps README, REST_API /info
2026-04-16 19:59:20 +02:00
..

API Documentation

Complete API reference for TimeTracker REST API.

📖 Overview

TimeTracker provides a comprehensive REST API for programmatic access to all features. The API supports token-based authentication and follows RESTful principles.

📚 Documentation

🔑 Quick Start

  1. Create an API token in Admin → Security & Access → Api-tokens (or /admin/api-tokens)
  2. Include the token in the Authorization header: Bearer YOUR_TOKEN
  3. Make requests to the API endpoints
  4. Review the API Token Scopes to ensure your token has the required permissions

📋 API Endpoints

See the REST API documentation for a complete list of available endpoints organized by resource type.