Retrieve a single lab order by its numeric id.
- Mock serverhttps://api-docs.lobbie.com/_mock/openapi/partner/v2/account/{accountId}/location/{locationId}/lab-order/{labOrderId}
- Productionhttps://api-prod.lobbie.com/lobbie/api/partner/v2/account/{accountId}/location/{locationId}/lab-order/{labOrderId}
curl -i -X GET \
'https://api-docs.lobbie.com/_mock/openapi/partner/v2/account/{accountId}/location/{locationId}/lab-order/9001' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'x-api-key: YOUR_API_KEY_HERE'Lab order retrieved successfully
Id of the linked /lab record, so a partner can navigate to the existing lab read view
Lifecycle status of a lab order, from staff placement through partner fulfilment. The server owns every transition; the partner never sets the status directly. SUBMITTED: placed by staff and awaiting partner pickup. ACCEPTED: the partner acknowledged the order and recorded its thirdPartyLabId. REJECTED: the partner declined the order; terminal, staff correct and re-release as a new order. PARTIALLY_RESULTED: some ordered tests have results, others are still pending. RESULTED: every ordered test has a final result. CORRECTED: a previously delivered result was superseded by a correction. CANCELLED: the order was cancelled before fulfilment.
Lab-assigned order identifier (accession / requisition number); null until the order is accepted
{ "createdAt": "2025-01-15T14:00:00Z", "id": 9001, "labId": 12345, "locationId": 200, "orderNumber": "ORD-100245", "orderingProviderId": 412, "patientId": 300, "status": "SUBMITTED", "tests": [ { … } ], "thirdPartyLabId": "ACC-8837162", "updatedAt": "2025-01-15T14:00:00Z" }