# Get Current Running Tracker Data Get current running tracker actual time data for a user. Only workspace owners and executive managers can use this endpoint. They can get tracker data for any member in their workspace. Important: This endpoint only works when the tracker is running from the API or from the browser. In other cases, it will not retrieve current tracking information. Endpoint: GET /time-tracking/current-data Version: 2.0.0 Security: oauth2, apiKey ## Query parameters: - `workspace_id` (integer, required) ID of the workspace Example: 1 - `user_id` (integer, required) ID of the user to get tracker data for. Must be a member of the specified workspace. Example: 100 ## Response 200 fields (application/json): - `success` (boolean) Example: true - `data` (object) Current tracker data including total time tracked. The total_minutes field combines minutes from Timeline entries for the date with minutes from the current running tracker. The total_seconds field represents the remainder seconds from the current tracker. - `data.contract_id` (integer,null) Contract ID (project-member assignment) if tracking with a project Example: 598672 - `data.user_id` (integer) User ID of the person tracking time Example: 45696 - `data.activity_description` (string,null) Description of the activity being tracked Example: "Working on API documentation" - `data.task_id` (integer,null) Task ID if tracking with a task Example: 3917798 - `data.task_title` (string,null) Title of the task if tracking with a task Example: "Adding timesheets" - `data.total_seconds` (integer) Remainder seconds from the current running tracker (after converting to minutes) Example: 9 - `data.total_minutes` (integer) Total minutes tracked, combining Timeline entries for the date with minutes from the current running tracker Example: 7 - `data.date` (string) Date of the tracking session Example: "2025-12-08" - `message` (string) Example: "Current tracker data retrieved successfully" - `meta` (object) - `meta.api_version` (string) Example: "2.0.0" - `meta.timestamp` (string) ## Response 400 fields (application/json): - `success` (boolean, required) - `message` (string, required) Error message describing what went wrong Example: "An error occurred" - `error` (string,null) Optional additional error details Example: "Internal Server Error" - `meta` (object, required) - `meta.api_version` (string) Example: "2.0.0" - `meta.timestamp` (string) ## Response 401 fields (application/json): - `success` (boolean, required) - `message` (string, required) Error message describing what went wrong Example: "An error occurred" - `error` (string,null) Optional additional error details Example: "Internal Server Error" - `meta` (object, required) - `meta.api_version` (string) Example: "2.0.0" - `meta.timestamp` (string) ## Response 403 fields (application/json): - `success` (boolean, required) - `message` (string, required) Error message describing what went wrong Example: "An error occurred" - `error` (string,null) Optional additional error details Example: "Internal Server Error" - `meta` (object, required) - `meta.api_version` (string) Example: "2.0.0" - `meta.timestamp` (string) ## Response 404 fields (application/json): - `success` (boolean, required) - `message` (string, required) Error message describing what went wrong Example: "An error occurred" - `error` (string,null) Optional additional error details Example: "Internal Server Error" - `meta` (object, required) - `meta.api_version` (string) Example: "2.0.0" - `meta.timestamp` (string) ## Response 500 fields (application/json): - `success` (boolean, required) - `message` (string, required) Error message describing what went wrong Example: "An error occurred" - `error` (string,null) Optional additional error details Example: "Internal Server Error" - `meta` (object, required) - `meta.api_version` (string) Example: "2.0.0" - `meta.timestamp` (string)