Time Tracking
Public API
Update Configuration
Changed onUpdates a time tracking configuration using JSON Merge Patch (RFC 7396) semantics: only the properties present in the body are applied, omitted properties are unchanged, and an explicit null clears a nullable property. Both GLOBAL and GROUP configurations can be updated. Content-Type: application/merge-patch+json is preferred because it names those semantics, but application/json is also accepted.
OAuth Scopes: time_tracking:configurations.write
patch/api/v1/time-tracking/configurations/{id}
Request
- Base URLhttps://companySubDomain.bamboohr.com
- Auth
- HTTP basic
- or OAuth 2Authorization code/authorize.phpToken URL/token.phpScopestime_tracking:configurations.write
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
idinteger required
The time tracking configuration ID.
Request body
Example request
{
"name": "Clock Entry",
"timesheetType": "CLOCK",
"workWeekStartsOn": "SUNDAY",
"approverType": "SPECIFIC_PERSON",
"approverUserId": 2274,
"approvalCutoff": "12:00",
"clockInSchedulePolicy": "ANYTIME",
"customOvertimeEnabled": true,
"overtimeDailyHours": "8.00",
"overtimeDailyDoubleHours": "12.00",
"overtimeWeeklyHours": "45.00"
}Response
The updated configuration.
Example response
{
"id": 3,
"name": "Clock Entry",
"type": "GROUP",
"timesheetType": "CLOCK",
"workWeekStartsOn": "SUNDAY",
"approverType": "SPECIFIC_PERSON",
"approverUserId": 2274,
"approvalCutoff": "12:00",
"clockInSchedulePolicy": "ANYTIME",
"customOvertimeEnabled": true,
"overtimeDailyHours": "8.00",
"overtimeDailyDoubleHours": "12.00",
"overtimeWeeklyHours": "45.00",
"employeeIds": [
101,
102,
103
],
"createdAt": "2025-06-12T14:57:06Z",
"updatedAt": "2026-03-10T20:28:42Z"
}Changes
- info
endpoint added
- info