timesheets.update

Fix a time entry that is not approved: its start, end, category, job, visit or notes. A rejected entry goes back to waiting for approval. A running clock's end is set with timesheets.clockOut. Approved time is locked; the owner can reopen it with timesheets.reopen.


Who	Agents can call this
REST	`POST /v1/timesheets/update`
MCP tool	`timesheets_update`
Writes	yes, send an Idempotency-Key
Area	Field work (checklists, forms, time, notes, change orders, subcontractors)

When to use it

Keep the crew's time: timesheets.clockIn starts a clock on a job (category work) or for drive, shop or break time, and timesheets.clockOut stops it; one clock runs per person per shop (pass stop_running to switch). Forgotten time goes in with timesheets.add (start and end, at most 24 hours per entry); time never overlaps the same person's other time.

What to tell the owner

Say what you did in plain words and what happens next.

Input

Field	Type	Required
`time_entry_id`	string (uuid)	yes
`started_at`	string (date-time)	no
`ended_at`	string (date-time)	no
`category`	string (one of work, drive, shop, break)	no
`job_id`	['string', 'null', ' ', '(', 'u', 'u', 'i', 'd', ')']	no
`visit_id`	['string', 'null', ' ', '(', 'u', 'u', 'i', 'd', ')']	no
`notes`	string	no

Example

POST https://doingwork.work/v1/timesheets/update
content-type: application/json
Idempotency-Key: 3f1c...

{
  "time_entry_id": "00000000-0000-4000-8000-000000000000"
}

Output

JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are {code, message, status}.

Errors

Code	Status	What to do
`invalid_input`, `invalid_token`, `rate_limited`		Can happen on any call. See errors.