Skip to main content
Money flows through two objects: proposals (quotes the buyer approves before work proceeds) and invoices (the bill for completed work). Suppliers create both through this API.
Neither endpoint is available to internal-service-team keys; quoting and invoicing are for third-party suppliers billing a buyer.
All examples assume:

Money is strings, in sections

Proposals and invoices share a line-item structure. Amounts are strings that must parse as numbers (“450.00”, not 450.00 as a float; format with two decimals and parse as decimals). The sections are labor, material, travel, freight, and misc (proposals add incurred cost). Each section carries its own line items, tax rate, and ...TotalBeforeTax, and the sections roll up to before-tax, tax, and after-tax totals. Travel, freight, and misc lines are simple { "description", "amount" } objects.

Proposals (quotes)

POST /v1/supplier/quote/proposals creates the proposal directly in pending status under your facility; there is no separate submit step. Required: workOrderId and totalAfterTax.
Behavior to know:
  • locationId, buyerFacilityId, and buyerCompanyId are derived from the work order; you cannot set them.
  • Unset tax fields and section totals default to "0".
  • requestForProposalId defaults to the work order’s RFP when omitted.
  • proposalPdfLink, if sent, must be a valid URL. attachments take FileDetails from the file upload endpoint.
  • Passing an id updates an existing proposal.
Track the outcome by re-fetching: status moves from pending to awarded or declined (decline reasons appear in declineNotes). List with GET /v1/supplier/quote/proposals (see filtering lists), read one with GET /v1/supplier/quote/proposals/{id}.

Invoices

The lifecycle

Invoices start as draft (invisible to the buyer) and get published into pending. The buyer then moves them through approved and processing to paid (or disputes them). Your integration creates the draft and publishes it; from pending onward you are mostly reading status.

Create the draft

POST /v1/supplier/invoice/invoices requires workOrderId; locationId, buyerFacilityId, buyerCompanyId, spendCategoryId, and problemTypeId are all derived from it.
Behavior to know:
  • poNumber defaults to the work order’s PO number.
  • serviceCallIds defaults to all service calls on the work order when omitted or empty; set it explicitly when billing a subset of visits.
  • OpenWrench validates taxLineItems against the invoice currency’s allowed tax types and rejects anything else. Currently only CAD supports them (GST/HST/PST).
  • invoicePDFLink (a valid URL) becomes the invoice’s single PDF entry if you host the PDF yourself; most integrations use the upload endpoint below instead.
  • autoPublishOnApproval opts this invoice into auto-publishing when the work order completes.
  • Saving an invoice can transition the associated work order’s status per the invoice-to-work-order status mapping. A save-level validation failure returns 406.
  • Passing an id updates an existing invoice (drafts only, in practice; buyer-side statuses are not yours to edit).

Upload the PDF and publish

POST /v1/supplier/invoice/file/upload_and_publish/{invoiceId} does both steps at once: the uploaded PDF (multipart part file, max 512 MB) becomes the invoice’s single PDF, and the status moves to pending.
The endpoint returns 400 if any precondition fails: your facility must own the invoice, the associated work order must be in Completed display status, and the buyer’s configuration must allow supplier invoice editing.

Read and reconcile

GET /v1/supplier/invoice/invoices (filterable, see filtering lists) and GET /v1/supplier/invoice/invoices/{id}. Third-party suppliers see masked records with buyer-private fields blanked. Poll status to drive your accounts receivable (AR) ledger: approvedAt, processedAt, and markedPaidAt timestamp the buyer’s progress.

Filtering lists

GET /v1/supplier/quote/proposals and GET /v1/supplier/invoice/invoices take offset, limit (default 10, max 25), sort_by, and order, plus the filters below. Filters combine with AND, and always combine with your key’s tenant scoping, so you only see your facility’s proposals and invoices. Neither list has a count endpoint; the response’s count is the total number of matches.
Both lists Proposals only Invoices only Value rules:
  • Sorting. Both lists sort by createdAt, id, workOrderId, locationId, supplierFacilityId, or buyerFacilityId; invoices also sort by invoiceTotalAfterTax, and proposals by updatedAt and totalAfterTax. Once you set sort_by, order defaults to asc, so send order=desc for newest first. With no sort_by, invoices come newest first and proposals come in id order (oldest first). An unsupported sort_by on proposals also falls back to id order.
  • Lists take commas with no spaces. A singular key (status) takes one value; the plural key takes a comma-separated list. status=pending,approved looks for one status with that literal name and returns nothing. A space after a comma can fail the request.
  • One value per key. If you repeat a parameter, only the first is used.
  • Dates use MM/dd/yyyy HH:mm:ss, for example 08/01/2026 00:00:00. The value is a local wall-clock time, read in the zone you pass in timezone, or in UTC without it. The time is required. The start bound is inclusive at the time you send. The end bound covers the whole end day in that zone: OpenWrench replaces its time with 23:59:59. URL-encode the value. Don’t add an offset such as -05:00 to the value: OpenWrench ignores it.
  • A date that doesn’t parse returns 400 with Invalid <key>. 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.
  • timezone takes an IANA zone name, such as America/Chicago or UTC. Fixed offsets (-05:00, GMT-5), abbreviations (CST), and unknown names return 400. See Date formats for daylight saving time.
  • Values must be well formed. A non-numeric id, or a boolean other than true or false, can fail the request with a 500 rather than a 400.
  • Unrecognized filters are ignored, and your tenant scoping can’t be overridden: supplierFacilityId is always set from your API key.
To match one local day, send the same date for both bounds along with your zone. This request returns invoices marked paid on October 9, 2026, Central time:

End-to-end billing flow

  1. Work order reaches quoting: submit a proposal, wait for awarded.
  2. Complete the work through service-call check-out.
  3. Create the draft invoice; generate your PDF.
  4. Once the work order shows Completed, upload_and_publish.
  5. Poll invoice status until paid, and reconcile against markedPaidAt.