Skip to main content
PATCH
Append a note to a work order

Autorizaciones

X-API-KEY
string
header
requerido
OW-KEY
string
header
requerido

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

Cuerpo

application/json

Verified payload: the work order id plus a single optional note object. note.text and note.noteAddedBy are the meaningful fields; noteAddedAt is overwritten with the server's current time, and the author's email is added to the work order's supplier subscriber list.

id
integer<int64>
requerido

Work order id (required; must exist)

note
object

Work-order note (abridged - additional media/caption/transcription fields exist).

taggedUsers
string<email>[]

Contact email addresses to @mention on the note. Each email is trimmed, lowercased and validated, then folded into note.elements as a user element, so you do not need to build the elements structure yourself. Duplicates in the list and users already tagged in note.elements are skipped. Requires a note object to tag people on. An entry that is not a valid email address, or a list of more than 25 emails, is rejected with 400 invalidInputDataException and nothing is persisted. An empty list is ignored.

Maximum array length: 25

Respuesta

Successful response

type
string
requerido

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
requerido

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>
requerido

"ok" on success

Opciones disponibles:
ok