POST
Workdiary.CustomerTime.List
List customer working-time (time_counter) rows for one team member on one date. Same data as the Work diary customer-hours popup. Distinct from WorkingTime.List (which is the customer-profile timer API).
Permissions
- User must be logged in with a valid bearer token.
- Returned or changed records are limited by the user permissions, team access, folder access, and account settings.
Action
- Runs the Workdiary.CustomerTime.List function and returns JSON.
Push Service
No push is sent because this function only reads data or returns helper information.
Automation
No automation is run for this function.
Special Instructions
- Send the bearer token on protected calls with Authorization: Bearer YOUR TOKEN.
- Send parameters as POST body fields exactly as documented.
- For paging, do not request more than 25 rows.
- For total rows, call the matching Count function with the same filters.
Required Parameters
No body parameters are required for this function.
Optional Parameters
| Name | Type | Sample | What it gives |
|---|---|---|---|
data_idpost | int | 211 | Team member id (creatd_by). Defaults to the logged-in user. Alias: user_id. |
selected_datepost | date | 2026-08-20 | Day YYYY-MM-DD. Send date filters and date values as UTC Y-m-d H:i:s when the route accepts date/time; date-only table columns store the Y-m-d date part. |
filter_namepost | string | Acme | Customer name contains. Alias: customer_name. |
row_data_idpost | int | 55 | Optional team_hours id to include team-member hours total. Alias: team_hours_id. |
limitpost | int | 25 | Maximum rows to return. Values above 25 are capped. |
Authentication
Send the bearer token returned by Login in the request header.
Authorization: Bearer YOUR TOKEN
Sample Request
{
"url": "\/app\/Workdiary.CustomerTime.List",
"method": "POST",
"headers": {
"Authorization": "Bearer YOUR TOKEN"
},
"body": {
"data_id": "211",
"selected_date": "2026-08-20"
},
"url_user": "https:\/\/{user}.bull36.com\/app\/Workdiary.CustomerTime.List",
"url_domain": "https:\/\/{domain}\/app\/Workdiary.CustomerTime.List"
}Endpoint
POST /app/Workdiary.CustomerTime.List
POST https://{user}.bull36.com/app/Workdiary.CustomerTime.List
POST https://{domain}/app/Workdiary.CustomerTime.ListSample Output
{
"success": 1,
"count": 1,
"data": [
{
"id": 10,
"customer_name": "Acme",
"total_hours": "1:30",
"category": "support"
}
]
}Count Only
Use the matching count route with the same filters when the UI only needs total rows for paging.
{
"url": "\/app\/Workdiary.CustomerTime.Count",
"url_user": "https:\/\/{user}.bull36.com\/app\/Workdiary.CustomerTime.Count",
"url_domain": "https:\/\/{domain}\/app\/Workdiary.CustomerTime.Count",
"method": "POST",
"headers": {
"Authorization": "Bearer YOUR TOKEN"
},
"body": {
"data_id": "211",
"selected_date": "2026-08-20"
},
"sample_output": {
"success": 1,
"count": 123
},
"notes": {
"count": "Use the matching count route when available, or count returned rows.",
"max_limit": 25
}
}Count JavaScript
const token = 'YOUR TOKEN';
const body = new URLSearchParams();
body.set('data_id', '211');
body.set('selected_date', '2026-08-20');
const res = await fetch('https://{domain}/app/Workdiary.CustomerTime.Count', {
method: 'POST',
headers: { Authorization: `Bearer ${token}` },
body
});
const data = await res.json();
console.log(data.count);JavaScript Example
const token = 'YOUR TOKEN';
const body = new URLSearchParams({ data_id: '211', selected_date: '2026-08-20' });
const res = await fetch('/app/Workdiary.CustomerTime.List', { method: 'POST', headers: { Authorization: 'Bearer ' + token }, body });
console.log(await res.json());Error Example
{
"success": 0,
"message": "Team member not found"
}