Search a customer's projects for time tracking
Lists one customer's projects that have at least one task, matched by name or number, newest project first.
The project picker after a customer was chosen. Customer is always filled on every entity.
Use it to:
- Customer → project → task cascade in a time-tracking client (customer from
GET /v1/customer/search-for-time-tracking)
Not for:
- The caller's own allocated projects of a customer →
GET /v1/project-header/search-for-time-tracking-by-customer-id-order-by-recent-registration
Behaviour:
- Idempotent.
- Safe to retry.
- Consistency: eventual
Call first: GET /v1/customer/search-for-time-tracking
Next: POST /v1/time-registration
See also: GET /v1/project-header/search-for-time-tracking, GET /v1/project-header/search-for-time-tracking-by-customer-id-order-by-recent-registration
Not yet documented: behaviour → consistency; examples; request → query params.
curl -X GET "https://app3.timelog.com/your-account/api/v1/project-header/search-for-time-tracking-by-customer-id?customerID=123&searchText=%22%22&searchAll=false&$page=1&$pagesize=10" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN"
import requests
import json
url = "https://app3.timelog.com/your-account/api/v1/project-header/search-for-time-tracking-by-customer-id?customerID=123&searchText=%22%22&searchAll=false&$page=1&$pagesize=10"
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/v1/project-header/search-for-time-tracking-by-customer-id?customerID=123&searchText=%22%22&searchAll=false&$page=1&$pagesize=10", {
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/v1/project-header/search-for-time-tracking-by-customer-id?customerID=123&searchText=%22%22&searchAll=false&$page=1&$pagesize=10", 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/v1/project-header/search-for-time-tracking-by-customer-id?customerID=123&searchText=%22%22&searchAll=false&$page=1&$pagesize=10')
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
{
"Properties": {
"TotalRecord": "example_string",
"TotalPage": "example_string",
"PageNumber": "example_string"
},
"Entities": [
{
"Properties": {
"ProjectID": 123,
"ID": "123e4567-e89b-12d3-a456-426614174000",
"Name": "John Doe",
"No": "example_string",
"ExpenseIsBillable": "null",
"CustomerID": 123,
"Customer": {
"CustomerID": 123,
"ID": "123e4567-e89b-12d3-a456-426614174000",
"Name": "John Doe",
"No": "example_string",
"DefaultMileageDistance": 25,
"CustomerStatusID": 123,
"VATNo": "example_string",
"OrganizationNo": "example_string"
},
"MainContractId": 123
},
"Links": [
{
"Href": "example_string",
"Rel": "example_string"
}
],
"Actions": [
{}
]
}
],
"Links": [
{
"Href": "example_string",
"Rel": "example_string"
}
]
}
{
"error": "Unauthorized",
"message": "Authentication required. Please provide a valid API token",
"code": 401
}
{
"error": "Forbidden",
"message": "You don't have permission to access this resource",
"code": 403
}
{
"Message": "No HTTP resource was found that matches the request URI 'https://app{server-number}.timelog.com/{account}/api/v1/project-header/search-for-time-tracking-by-customer-id'.",
"MessageDetail": "No action was found on the controller 'ProjectHeader' that matches the request."
}
{
"error": "Internal Server Error",
"message": "An unexpected error occurred on the server",
"code": 500,
"requestId": "req_1234567890"
}
/v1/project-header/search-for-time-tracking-by-customer-id
Target 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.Customer whose projects are returned. Omitted → 404 (no action matched). Unknown ID → empty list.
Filters on ProjectHeaderRead.CustomerID (eq).
Substring matched against project name and number (LIKE '%text%'). Empty = no text filter.
Filters on ProjectHeaderRead.Name | ProjectHeaderRead.No (contains).
Needs privilege RegistrationAllTasks. Has no effect on the rows returned.
Page number.
Page size. No maximum enforced in the API layer.
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.
Query Parameters
Customer whose projects are returned. Omitted → 404 (no action matched). Unknown ID → empty list.
Filters on ProjectHeaderRead.CustomerID (eq).
Substring matched against project name and number (LIKE '%text%'). Empty = no text filter.
Filters on ProjectHeaderRead.Name | ProjectHeaderRead.No (contains).
Needs privilege RegistrationAllTasks. Has no effect on the rows returned.
Page number.
Page size. No maximum enforced in the API layer.
Responses
Paging values. They are returned as STRINGS, for example "TotalRecord": "12".
Omitted (not []) when the list is empty.