---
title: "Update Work Order Fields"
method: PATCH
path: "/service_orders/{purchase_order_uid}"
---

# Update Work Order Fields

`PATCH /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. This is a narrower field set than the full PUT update — intended for lightweight edits (title, dates, remarks, vendor/payment term) without resending the whole order. Work Orders (Service Orders) may change `vendor` (the assigned subcontractor) through this endpoint.

## Path parameters

- `purchase_order_uid` string, required

## Request body

- object
  - `purchase_order_title` string
  - `reference_number` string
  - `remarks` string
  - `due_date` string, date
  - `delivery_time` 'ANYTIME' | 'MORNING' | 'AFTERNOON' | 'SPECIAL_REQUEST'
  - `vendor` string: Work Orders (Service Orders) may change `vendor` (the assigned subcontractor) through this endpoint.
  - `payment_term` string
  - `template` string
  - `job_measurement_uids` string[]
  - `job_attachments_uids` string[]

## Response `200`

200

- object
  - `type` 'success'
  - `title` string
  - `message` string

## 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/patch.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)