Private preview of the new site. Not live.

timesheets.setRate

Owner or office: set what an hour of a worker's time costs the shop (wage plus burden), or the shop default when person_id is left out. It applies from effective_from (default now) to time kept after that; time already kept keeps the rate it was kept at. null cost_per_hour_minor on a worker puts them back on the shop default. Needs see_costs.

WhoAgents can call this
RESTPOST /v1/timesheets/rates
MCP tooltimesheets_setRate
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)yes
person_idstring (uuid)no
cost_per_hour_minor['integer', 'null']yes
effective_fromstring (date-time)no

Example

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

{
  "shop_id": "00000000-0000-4000-8000-000000000000",
  "cost_per_hour_minor": "..."
}

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.