> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/deployment-and-it-ops/integrations-and-api-access/integrations/oauth-for-direct-api-access/project-suite/task-timelog-report-api.md).

# 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

```http
POST https://api.in.we360.ai/query/external/reports/task_timelog_report
```

### Request body

```json
{
  "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
}
```

| Parameter                | Required | Description                                                            |
| ------------------------ | -------- | ---------------------------------------------------------------------- |
| `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

```json
{
  "data": [
    {
      "task_id": "c7d8e9f0-aaaa-bbbb-cccc-ddddeeeeffff",
      "task_key": "ACME-142",
      "task_summary": "Draft deposition outline",
      "task_type": "TASK",
      "task_status": "IN_PROGRESS",
      "project_id": "a1b2c3d4-1111-2222-3333-444455556666",
      "project_name": "Case 4821 — Acme Litigation",
      "identity_id": "f9c8f8f8-1111-2222-3333-444455556666",
      "employee_id": "EMP-1024",
      "log_date": "2026-04-02",
      "logged_duration": "02:30:00",
      "is_billable": true
    }
  ],
  "pagination": { "page": 1, "limit": 50, "total_records": 184, "total_pages": 4, "has_next": true, "has_previous": false },
  "meta": { "mode": "detailed", "selected_columns": ["task_id", "task_key", "task_summary", "log_date", "logged_duration"] }
}
```

### Example

```bash
curl -X POST "https://api.in.we360.ai/query/external/reports/task_timelog_report" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer ${access_token}" \
  -d '{"start_date":"2026-04-01T00:00:00","end_date":"2026-04-30T23:59:59","mode":"detailed","columns":["task_key","task_summary","project_name","employee_id","log_date","logged_duration","is_billable","approval_status"],"project_id":"a1b2c3d4-1111-2222-3333-444455556666","page":1,"limit":100}'
```

Use `summary` for estimate-versus-actual reporting. Use `detailed` for billing exports. Invalid columns or filters return validation errors.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.we360.ai/deployment-and-it-ops/integrations-and-api-access/integrations/oauth-for-direct-api-access/project-suite/task-timelog-report-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
