PerspioTalk uses the standard HTTP methods. Request and response bodies are JSON unless an endpoint says otherwise.

Method	Used to
`GET`	Read one resource by ID, or list resources
`POST`	Create a resource, run an action such as Archive Asset or Copy Workflow, or start a job
`PUT`	Replace a resource. Send the complete object
`PATCH`	Change specific fields with a JSON Patch document
`DELETE`	Delete a resource

Updating a resource

Endpoints update resources in different ways, so check the method on the endpoint page:

PUT replaces the whole resource. Most update endpoints work this way.
PATCH changes only the fields you name.
POST is used by a few endpoints, such as Update Asset and Update Workflow.

PUT: send the complete object

A PUT replaces the stored resource with the body you send, so any field you leave out is cleared. The safe pattern is:

GET the resource.
Change the fields you need in that response.
PUT the whole object back. The ID stays the same.

PATCH: send a JSON Patch document

PATCH endpoints take a JSON Patch document: an array of operations, each naming a field by its path. This body for Update Device sets two fields and leaves everything else unchanged:

[
  { "op": "replace", "path": "/runHoursOffset", "value": 100 },
  { "op": "replace", "path": "/odometerOffset", "value": -100 }
]

Property	Meaning
`op`	The operation. `replace` changes a value; `add` and `remove` change lists, such as group memberships
`path`	The field to change, as a JSON Pointer starting with `/`
`value`	The new value. Not needed for `remove`

Each PATCH endpoint's page shows the body it expects. The one exception to JSON Patch is Update Current User Access, which takes the changed fields as plain JSON.