Two endpoint families answer “who can do this work”: the supplier facilities listing (your whole network) and the ranked private-network endpoint (the ordered shortlist for one location and problem type). Together with the work order reassignment patch, they let you automate dispatch.
All examples assume:
Your supplier network
GET /v1/buyer/supplier_facilities returns every non-deleted supplier relationship for your company. Unlike most list endpoints, it supports a documented filter set:
Fetch one facility with GET /v1/buyer/supplier_facilities/{id}.
Ranked private-network suppliers
For automated dispatch, ask for the ranked list for a (location, problemType) pair:
GET /v1/buyer/private_network/buyer_supplier_relationships/ranked/{locationId}/{problemTypeId} returns buyer–supplier relationships, each hydrated with your relationship details (contacts and routing emails).
Rank is conveyed by array order. Any sort_by you pass is deliberately dropped so that array order always equals rank. The endpoint is paginated (default 10, max 25 per page), so rank continues across pages: the first item of page two is rank 11.
Automated dispatch pattern
- A work order comes in (or is created unassigned).
- Call the ranked endpoint for the work order’s
locationId and problemTypeId.
- Take the first relationship’s supplier facility and assign it, either at creation time (
supplierFacilityId on the create body) or afterwards with PATCH /v1/buyer/work_order/work_orders/{id}.
- If the supplier declines, the work order returns to
PendingApproval (or a private-network supplier may be auto-picked, per your configuration). On decline, re-run the ranking and assign the next candidate.
Escalation ladders, response-time SLAs, and decline counts can all be layered on top of this loop; the ranking endpoint gives you the ordered candidates, and the work order’s statusChanges tell you how each attempt went. 
