ZUzuper

Work Order Bulk Action

Changed on

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. Only action: "update_status" is currently supported. The action is processed asynchronously by a background worker — this endpoint acknowledges the request immediately; it does not confirm that every order was updated by the time it responds.

post/service_orders/bulk_action

Request

  • Base URL
    https://dc-region.zuperpro.com/api
  • URL
    https://dc-region.zuperpro.com/api/service_orders/bulk_action
  • Auth
    API key in header x-api-key

Request body

purchase_order_uidstring[]

UIDs to target. Alternative to filter_rules.

filter_rulesobject[]

Rule-engine filter, alternative to purchase_order_uid.

filter_rule_operator'AND' | 'OR'
action'update_status' required

Response

200

type'success'
titlestring
messagestring

Changes