---
title: "Get Work Order Details"
method: GET
path: "/service_orders/{purchase_order_uid}"
---

# Get Work Order Details

`GET /service_orders/{purchase_order_uid}`

## Request

- Base URL: `https://dc-region.zuperpro.com/api`
- URL: `https://dc-region.zuperpro.com/api/service_orders/{purchase_order_uid}`
- Auth: API key in header `x-api-key`

Operates on Service Orders, shown in the Zuper client app as "Work Order" (in every industry). Work Orders share the exact same underlying schema and endpoints as Purchase Orders / Material Orders; they're distinguished only by the `purchase_order_type` field (`SERVICE_ORDER` here) and the `/service_orders` route prefix. A UID belonging to the other module (e.g. a Work Order UID fetched via `/purchase_orders/:uid`) returns 404.

## Path parameters

- `purchase_order_uid` string, required

## Query parameters

- `fields_to_select` string

## Response `200`

200

- object
  - `type` 'success'
  - `title` string
  - `message` string
  - `data` object: Full document with populated references: job, estimate, asset, vendor, material_request, ship_to.product_location, project, parent_po, template, payment_term, line_items.product_ref_id, line_items.vendor_catalog, approval.await_approval, and appointments (expanded from UIDs to summaries).

## Changes

- **2026-11-03** `3c21bc232e16`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/zuper/apis/zuper-pro-api/changes/service_orders/:purchase_order_uid/get.md)

---

[API](https://skmtc.dev/zuper/apis/zuper-pro-api.md) - [All operations](https://skmtc.dev/zuper/apis/zuper-pro-api/llms.txt) - [OpenAPI document](https://skmtc.dev/zuper/apis/zuper-pro-api/revisions/3c21bc232e16?raw)