Private preview of the new site. Not live.

timesheets.clockIn

Start a person's clock: on a job (work), or drive, shop or break time. A field worker clocks only themself, and on a visit only when assigned to it; the owner or office can clock in anyone. One running clock per person per shop: pass stop_running to stop the running one first (for example to switch from drive to work).

WhoAgents can call this
RESTPOST /v1/timesheets/clock-in
MCP tooltimesheets_clockIn
Writesyes, send an Idempotency-Key
AreaField 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

FieldTypeRequired
shop_idstring (uuid)no
job_idstring (uuid)no
visit_idstring (uuid)no
person_idstring (uuid)no
categorystring (one of work, drive, shop, break)no
notesstringno
stop_runningbooleanno

Example

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

{
  "shop_id": "00000000-0000-4000-8000-000000000000",
  "job_id": "00000000-0000-4000-8000-000000000000",
  "visit_id": "00000000-0000-4000-8000-000000000000",
  "person_id": "00000000-0000-4000-8000-000000000000",
  "category": "work",
  "notes": "...",
  "stop_running": true
}

Output

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

Errors

CodeStatusWhat to do
invalid_input, invalid_token, rate_limitedCan happen on any call. See errors.