timesheets.add
Add time after the fact (a manual entry with a start and an end, at most 24 hours). It waits for approval like clocked time. It cannot overlap the person's other time.
| Who | Agents can call this |
| REST | POST /v1/timesheets |
| MCP tool | timesheets_add |
| 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 |
|---|---|---|
shop_id | string (uuid) | no |
job_id | string (uuid) | no |
visit_id | string (uuid) | no |
person_id | string (uuid) | no |
category | string (one of work, drive, shop, break) | no |
started_at | string (date-time) | yes |
ended_at | string (date-time) | yes |
notes | string | no |
Example
POST https://doingwork.work/v1/timesheets
content-type: application/json
Idempotency-Key: 3f1c...
{
"started_at": "...",
"ended_at": "..."
}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. |