timesheets.decide
Owner or office: approve or reject stopped time entries (up to 200 at once, one shop). Office staff cannot decide their own time; only the owner can. Approved time is locked and counts for payroll and job costing; rejected time goes back to the worker to fix (any fix puts it back to waiting). A note is kept with the decision.
| Who | Agents can call this |
| REST | POST /v1/timesheets/decide |
| MCP tool | timesheets_decide |
| 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_ids | array | yes |
decision | string (one of approve, reject) | yes |
note | string | no |
Example
POST https://doingwork.work/v1/timesheets/decide
content-type: application/json
Idempotency-Key: 3f1c...
{
"time_entry_ids": [
"00000000-0000-4000-8000-000000000000"
],
"decision": "approve"
}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. |