Base URL
/v1/partners/ path prefix.
Authentication
These endpoints require a partner API key — a separate credential from buyer and supplier API keys. A buyer API key will not work against/v1/partners/ endpoints, even though this section lives under the Buyer API docs.
Every request must carry two headers: X-API-KEY (the partner key) and OW-KEY (the OpenWrench shared secret issued alongside it). The key automatically scopes every request to your company’s data. Requests missing either header return 401.
Rate limits
10 requests per 20-second window per key. Beyond that you’ll receive429 Too Many Requests — back off and retry.
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). Additional query parameters are treated as field filters — pass a field name with a value (comma-separate multiple values) to filter the result set.
The purchasing flow
A typical integration follows the purchasing lifecycle: read approved purchase requests and their line items, create a purchase order against a vendor, associate PR line items to PO line items, mark the PO ordered, and record receipts as items arrive (negative received quantities record returns). Parts, equipment types, vendors, and stock locations round out the reference data.Detailed guides
Purchasing flow
The lifecycle end to end: requests, orders, line items, and receipts.
Catalog & stock
Parts, equipment, vendors, stock locations, and work order consumption.