Base URL
/v1/supplier/.
Authentication
Every request must carry two headers:X-API-KEY (your API key, issued per supplier contact) and OW-KEY (the OpenWrench shared secret issued alongside it). The key automatically scopes every request to your facility. You only ever see work orders, invoices, and data that belong to you. Requests missing either header return 401.
Rate limits
10 requests per 20-second window per key. Beyond that you’ll receive429 Too Many Requests. Wait at least 20 seconds before retrying, and space background jobs (such as full paginated exports) so they stay under the cap.
Keeping work orders in sync
Most supplier integrations exist to mirror the OpenWrench work order queue into another system. Build that on push, not polling:- Register a webhook endpoint. OpenWrench sends
workorder.create,workorder.status_update, andworkorder.new_noteevents as they happen. - On each event, fetch that one work order with
GET /v1/supplier/work_order/work_orders/{id}. - Use
GET /v1/supplier/work_order/work_ordersonly for the one-time initial load and for occasional reconciliation, with a narrow filter and a small page.
Response envelope
Single-entity responses:count:
401 means a missing or invalid key; 400 covers bad input, bad filters, and permission denials; 429 is the rate limit.
Pagination and filtering
List endpoints acceptoffset, limit (default 10, max 25), sort_by, and order (asc | desc). The API treats additional query parameters as filters. Each endpoint supports its own set of filter keys, and keys it does not recognize are ignored rather than rejected. Multi-value filters use a plural key with comma-separated values (statuses=TechScheduled,TechRescheduled). For work orders, see the filter reference.
Date formats
Most timestamps are ISO 8601 strings with offset (for example,2026-08-14T13:05:22.000-07:00); some database timestamp fields serialize as yyyy-MM-dd HH:mm:ss.S. Plain dates are yyyy-MM-dd.
When sending date-times, use ISO 8601 with a T between the date and time and an explicit offset. A space-separated value such as 2026-09-10 10:43:00+00:00 is not ISO 8601, and the API rejects it. Send 2026-09-10T10:43:00.000+00:00 instead. UTC may be written as +00:00 or Z.
Date filters on the invoice, proposal, and work order lists are the exception. They take MM/dd/yyyy HH:mm:ss, a local wall-clock time with no offset, for example 10/09/2026 00:00:00:
- Time zone. Pass the optional
timezonequery parameter to set the zone OpenWrench reads the values in. Use an IANA zone name, such asAmerica/Chicago,America/New_York, orUTC. Names are case-sensitive. Withouttimezone, OpenWrench reads values in UTC. - Rejected zones. Fixed offsets (
-05:00,GMT-5,Z,Etc/GMT+5), abbreviations (CST), and unknown names return400. - No offset in the value. OpenWrench ignores an offset such as
-05:00at the end of a filter value. Usetimezoneinstead. - Malformed values return
400. A value that doesn’t match the format returns400, for exampleInvalid markedPaidAtStartDate. Expected format MM/dd/yyyy HH:mm:ss. That includes ISO 8601 values (2026-10-09T00:00:00), dates without a time (10/09/2026), and values of only spaces. OpenWrench still reads an empty value as 1 January 1970. - End bounds. Invoice and proposal end dates cover the whole end day: OpenWrench replaces the time with 23:59:59 on that date in
timezone. Work order end dates are exact, so send23:59:59to include the whole day. - Daylight saving time. A time in the skipped hour of a spring-forward change moves forward by the length of the gap. A time in the repeated hour of a fall-back change means the standard-time occurrence, which is the second one.
Technician time data
The WrenchMode endpoints expose per-technician work and drive time:GET /v1/supplier/wrench_mode/events/analytics/{fromDate}/{toDate} returns a per-technician drive/work/total rollup (window capped at 1 month). GET /v1/supplier/wrench_mode/events returns the raw event log behind it. Service-call expansions (/with_work_logs, /with_tech_details) give the per-visit story.
Detailed guides
The guides in this tab walk each part of the API in depth, with payloads, status models, and integration patterns:Work orders
Receive, accept or decline, parts statuses, ECD, attachments, and notes.
Webhooks
New work, status changes, and buyer notes pushed to your endpoint.
Service calls
Schedule, check in, check out, and set the completion status.
WrenchMode
Per-technician analytics and the raw drive/work event log.
Quotes & invoicing
Submit proposals, draft invoices, and publish with a PDF.
Purchasing & inventory
Purchase requests to orders to receipts, catalogs, and stock.
Reference data
Buyer companies, locations, assets, and how data masking works.
Files & users
The file store behind attachments, and technician provisioning.