Skip to main content
PATCH
Append photo notes to a work order in bulk

Authorizations

X-API-KEY
string
header
required
OW-KEY
string
header
required

OpenWrench shared secret. Required on every request alongside X-API-KEY; issued together with your API key.

Body

application/json

The work order id plus 1-25 photo-only notes. Every note's noteAddedBy is set to the calling contact and noteAddedAt is overwritten with the server's current time; the author's email is added to the work order's supplier subscriber list.

id
integer<int64>
required

Work order id (required; must exist)

notes
object[]
required

Photo-only notes to append, in the order they should appear on the thread. Each entry must set photo and leave every other content field empty; photo URLs must be unique within the request.

Required array length: 1 - 25 elements

Response

Successful response

type
string
required

Entity type label, e.g. "WorkOrder". Endpoints that derive it via Scala reflection (most generic list/get endpoints) may return the fully qualified server class name instead (e.g. "models.workorder.WorkOrder"); treat this field as informational.

data
object
required

Work order (abridged - the full model has 150+ fields including hydrated location/asset/facility/approval-hierarchy objects). For third-party suppliers (keys not belonging to an internal service team) responses are masked: buyer-private fields are removed/blanked by the API masking layer.

status
enum<string>
required

"ok" on success

Available options:
ok