mirror of
https://github.com/DRYTRIX/TimeTracker.git
synced 2026-05-19 04:40:32 -05:00
6c8e86cd01
Timer starts always blocked a second running entry and never read the\nadmin-controlled Settings flag.\n\n- Add TimeTrackingService.can_start_timer() using Settings.get_settings()\n and wire it into start_timer, web timer routes, kiosk start, and\n legacy POST /api/timer/resume.\n- POST /api/v1/timer/start returns 409 with error_code\n timer_already_running when single-active mode is on and a timer\n is already running.\n- Deduplicate start_timer template handling in the service.\n\nTests: tests/test_single_active_timer_setting.py.\nDocs: REST_API (responses), GETTING_STARTED, REQUIREMENTS, Docker env\nnotes, TESTING_STRATEGY, env.example comment; CHANGELOG entry.
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
- REST API - Complete API reference with all endpoints
- Response Format - Standard error envelope and success/legacy response shapes
- API Token Scopes - Understanding token permissions and scopes
- API Versioning - API versioning strategy and best practices
- API Enhancements - Recent API improvements and additions
🔑 Quick Start
- Create an API token in Admin → Security & Access → Api-tokens (or
/admin/api-tokens) - Include the token in the
Authorizationheader:Bearer YOUR_TOKEN - Make requests to the API endpoints
- 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.