Per-technician analytics
GET /v1/supplier/wrench_mode/events/analytics/{fromDate}/{toDate} returns one row per technician with their drive time, work time, and total over the window.
- Both dates are
yyyy-MM-dd, and the window may span at most one month. Split longer ranges into month-sized calls. - Dates are UTC days unless you pass
timezone(see Time zones). OpenWrench checks the one-month cap on the dates as given, before it applies the zone. - The rollup covers your API key’s supplier facility. A key whose contact is not attached to a supplier facility gets
401.
The raw event log
GET /v1/supplier/wrench_mode/events returns the underlying events, tenant-scoped to your supplier. Filters:
Standard pagination (
offset, limit max 25, sort_by, order) applies except under scheduleId. One formatting trap: a present-but-empty CSV filter (for example eventTypes=,) is rejected as malformed rather than ignored.
began_trip through trip_cancelled, plus drive_note) and work events (started_work, ended_work, and the location_* timer events that mark pauses and resumes on site). Trip events may point to a home address instead of a location.
A home trip is a trip event (began_trip, trip_paused, trip_resumed, trip_cancelled, drive_note, or arrived) that has homeAddressId set and no locationId, workOrderId, or serviceCallId. Work events never carry homeAddressId. Because of this, locationId can be null on trip events.
Time zones
Both WrenchMode routes accept an optionaltimezone query parameter. It sets the zone that fromDate and toDate are read in, so a day matches your technicians’ local day instead of a UTC day.
- Pass an IANA zone name, such as
America/Chicago,America/New_York, orUTC. Names are case-sensitive. fromDatestarts at the beginning of that day in the zone.toDateincludes that whole day in the zone.- OpenWrench uses the zone’s real day boundaries. A daylight saving change day is 23 or 25 hours long.
- Without
timezone, dates are UTC days. - Fixed offsets (
-05:00,GMT-5,Z,Etc/GMT+5), abbreviations (CST), and unknown names return400.
timezone, the event falls on October 10. With timezone=America/Chicago, it falls on October 9:
Choosing between them
- Analytics for dashboards, payroll, and utilization reports: one number per technician per period, pause math already done.
- Raw events for auditing a suspicious total, reconstructing a visit minute-by-minute, or feeding your own analytics warehouse.
- Per-visit questions are usually better served by the service-call expansion
GET /v1/supplier/work_order/service_calls/{id}/with_work_logs. It returns exactly the events in the visit’s check-in/check-out window plus the pause-excludedtrueWorkTimeMillis. See Service calls.
Worked patterns
Weekly payroll pull. Every Monday, call analytics for the prior week, join on technician email against your payroll system, and use work + drive time as the paid-hours input. The drive home counts toward the drive-time total, even though it is not billed to any work order. One call per week per facility keeps you far under the rate limit. Monthly utilization report. Analytics with month boundaries (2026-08-01 to 2026-08-31 is within the one-month cap); divide work time by scheduled time from your rostering system.
Labor cost reconciliation on an invoice. For each service call on the invoiced work order, fetch /with_work_logs, sum trueWorkTimeMillis, and compare against the labor line items before the buyer ever sees a dispute.