Timeero

Update group

Changes data in the connected account. Update a group (rename or change its membership) Rename a group or replace who belongs to it. Supplying user_ids REPLACES the membership rather than adding to it, so read the group first and send the full intended list. Setting all_users to true puts every employee in the company into the group. (PUT /groups/{id})

Delete group

Changes data in the connected account. Delete a group Permanently delete a group from the company. The employees in it are not deleted, but the grouping and any manager visibility it provided are lost. (DELETE /groups/{id})

Create job

Changes data in the connected account. Create a job Create a new job for crews to clock into, e.g. when a new loss comes in. Check list_jobs for an existing match first so you do not create a duplicate for the same address. (POST /jobs)

Update job

Changes data in the connected account. Update a job (including closing it out) Update an existing job. Setting job_status to false deactivates the job, which is how a finished loss is closed out so crews stop clocking into it. `name` is required by the API even when you are only changing another field, so read the job first and send its current name back unchanged. (PUT /jobs/{id})

Delete job

Changes data in the connected account. Delete a job Permanently delete a job. Prefer update_job with job_status false to close out finished work: deleting a job discards it from the record, while deactivating preserves its history for job costing. (DELETE /jobs/{id})

Create task

Changes data in the connected account. Create a task Create a task employees can clock into within one or more jobs (e.g. demo, extraction, drying). (POST /tasks)

Update task

Changes data in the connected account. Update a task Update an existing task. `name` and `user_id` are required by the API even for a partial update, so read the task first and send its current values back unchanged. (PUT /tasks/{id})

Delete task

Changes data in the connected account. Delete a task Permanently delete a task from the company. (DELETE /tasks/{id})

Create timesheet

Changes data in the connected account. Create a timesheet entry (manual time entry) Add a completed or in-progress time entry for an employee, e.g. backfilling a shift a tech forgot to clock. To start a live shift instead, use clock_in_user. (POST /timesheets)

Delete timesheets

Changes data in the connected account. Delete timesheets in bulk Permanently delete one or more timesheet entries by id. Destructive and not recoverable through the API: confirm the exact ids with list_timesheets first, and prefer correcting an entry with update_timesheet over deleting it. (DELETE /timesheets)

Update timesheet

Changes data in the connected account. Update a timesheet entry (correct hours, job, or mileage) Correct an existing time entry: fix a clock-out someone forgot, move hours to the right job, or adjust mileage. `user_id` and `start` are required by the API even for a partial update, so read the entry first and send its current values back unchanged. (PUT /timesheets/{id})

Approve timesheets

Changes data in the connected account. Approve timesheets in bulk Mark one or more timesheet entries approved, the step that releases them for payroll. Approving is a payroll action: confirm the exact ids with list_timesheets (approved=false) and confirm the hours look right before calling this. (POST /timesheets/approve)