List a project's tasks for moving hours
Returns a project's active leaf tasks with their parent tasks, as a nested name / ID tree for choosing a move target.
Selects the project's ACTIVE leaf tasks (any task status) and adds all their ancestor tasks, then nests them: root tasks are the entities, sub-tasks sit in Items (recursively). Value = TaskID; Name = the task name, plus " (<task number>)" when the TaskNo feature is on and the task has a number. Parent tasks appear only as containers — time cannot be moved onto them (move / split refuse a parent task). Ordered by the project's task sort order. Unpaged. An unknown, 0 or negative projectId answers 200 with no Entities (captured).
Use it to:
- Pick TargetTaskId for PUT /v2/adjustments/move-hours or the split halves
Not for:
- Task search across projects →
GET /v1/task/filter
Behaviour:
- Idempotent.
- Safe to retry.
- Changes are visible to the next read immediately.
Call first: GET /v2/adjustments/move-hours/projects
Next: PUT /v2/adjustments/move-hours
See also: GET /v1/task
curl -X GET "https://app3.timelog.com/your-account/api/v2/adjustments/move-hours/projects/123/tasks" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN"
import requests
import json
url = "https://app3.timelog.com/your-account/api/v2/adjustments/move-hours/projects/123/tasks"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
response = requests.get(url, headers=headers)
print(response.json())
const response = await fetch("https://app3.timelog.com/your-account/api/v2/adjustments/move-hours/projects/123/tasks", {
method: "GET",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
)
func main() {
req, err := http.NewRequest("GET", "https://app3.timelog.com/your-account/api/v2/adjustments/move-hours/projects/123/tasks", nil)
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
fmt.Println("Response Status:", resp.Status)
}
require 'net/http'
require 'json'
uri = URI('https://app3.timelog.com/your-account/api/v2/adjustments/move-hours/projects/123/tasks')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
response = http.request(request)
puts response.body
{
"Entities": [
{
"Properties": {
"Name": "This is another test (0023)",
"Value": 52
}
},
{
"Properties": {
"Name": "Task 1",
"Value": 1
}
},
{
"Properties": {
"Name": "This is a test (0022)",
"Value": 51
}
},
{
"Properties": {
"Name": "Task 2",
"Value": 2
}
},
{
"Properties": {
"Name": "test task",
"Value": 16
}
}
],
"Links": [
{
"Href": "https://app{server-number}.timelog.com/{account}/api/v2/adjustments/move-hours/projects/1/tasks",
"Rel": "self"
}
]
}
{
"Links": [
{
"Href": "https://app{server-number}.timelog.com/{account}/api/v2/adjustments/move-hours/projects/99999999/tasks",
"Rel": "self"
}
]
}
{
"error": "Unauthorized",
"message": "Authentication required. Please provide a valid API token",
"code": 401
}
{
"error": "Not Found",
"message": "The requested resource was not found",
"code": 404
}
/v2/adjustments/move-hours/projects/{projectId}/tasksTarget server for requests. Edit to use your own host.
OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).
The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.
> Not yet documented: how to obtain a token.
> Not yet documented: token lifetime.
Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).
The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.
> Not yet documented: how to obtain a token.
> Not yet documented: token lifetime.The project. Not an integer → 404 with empty body (route constraint, captured); unknown / 0 / negative → 200 empty list (captured).
Request Preview
Response
Response will appear here after sending the request
Authentication
Bearer token. OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).
The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.
Not yet documented: how to obtain a token.
Not yet documented: token lifetime.
Path Parameters
The project. Not an integer → 404 with empty body (route constraint, captured); unknown / 0 / negative → 200 empty list (captured).
Responses
Omitted (not []) when the list is empty.