Task Timelog Report API
Retrieve task-level time logs with explicit field selection.
Retrieve task worklogs with explicit column selection. summary returns one row per task. detailed returns one row per time-log entry.
Endpoint
POST https://api.in.we360.ai/query/external/reports/task_timelog_reportRequest body
{
"start_date": "2026-04-01T00:00:00",
"end_date": "2026-04-30T23:59:59",
"mode": "detailed",
"columns": ["task_id", "task_key", "task_summary", "task_type", "task_status", "project_id", "project_name", "identity_id", "employee_id", "log_date", "logged_duration", "is_billable"],
"page": 1,
"limit": 50,
"project_id": "",
"task_id": "",
"user_id": "",
"group_id": "",
"task_type": [],
"task_status": [],
"billable": null
}start_date, end_date
Yes
ISO datetime range, filtered by log_date.
mode
Yes
summary returns task totals. detailed returns individual worklogs.
columns
Yes
Explicit fields to return.
page
No
Page number. Defaults to 1.
limit
No
Page size. Use 0 for all records.
project_id, task_id
No
Comma-separated project or task UUIDs.
user_id, group_id
No
Comma-separated user or group UUIDs.
task_type
No
Types such as ["EPIC","TASK","BUG"].
task_status
No
Statuses such as ["TODO","IN_PROGRESS","DONE"].
billable
No
true, false, or null for all records.
Available columns
Task:
task_id,task_key,task_summary,task_type,task_status,parent_id,project_id,project_name,reviewer_identity_id,reviewer_name.User:
identity_id,employee_id,first_name,last_name,email,group_name.Time:
estimated_duration,logged_duration,remaining_duration.Detailed mode:
time_log_id,log_date,start_time,end_time,is_billable,source,description,approval_status.
remaining_duration is available in summary mode. Durations use HH:MM:SS.
Response
Example
Use summary for estimate-versus-actual reporting. Use detailed for billing exports. Invalid columns or filters return validation errors.
Last updated
Was this helpful?