Update a system
const url = 'https://example.com/api/v1/systems/example';const options = { method: 'PATCH', headers: {'Content-Type': 'application/json'}, body: '{"display_name":"example","name":"example","standard_id":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PATCH \ --url https://example.com/api/v1/systems/example \ --header 'Content-Type: application/json' \ --data '{ "display_name": "example", "name": "example", "standard_id": "example" }'Patches a system’s display_name or standard. An omitted standard_id leaves it unchanged; an explicit empty string clears it, converting the system to a one-off. Gated by system:update; read and update scopes drive the 404 versus 403 split.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Request Body required
Section titled “Request Body required ”object
A URL to the JSON Schema for this object.
A new globally unique technical name (rename)
Responses
Section titled “ Responses ”OK
object
A URL to the JSON Schema for this object.
The scope-aware actions the caller may perform on this row (create a child, update, delete); a UI hint, the server still enforces.
The resolved effective tags (key -> winning value) that cascade onto this system (platform, its location, its system tree); for the Tags column.
object
The location’s name, for display
The location’s id, the canonical handle
How many components are bound into this system
The parent system’s name, for display; absent for a root system
The parent system’s id, the canonical handle
The standard’s handle, for display; omitted for a one-off system
The standard’s uuid; the stable form of standard
Example
{ "$schema": "/api/v1/schemas/SystemBody.json"}default
Section titled “default ”Error
object
A URL to the JSON Schema for this object.
A human-readable explanation specific to this occurrence of the problem.
Optional list of individual error details
object
Where the error occurred, e.g. ‘body.items[3].tags’ or ‘path.thing-id’
Error message text
The value at the given location
A URI reference that identifies the specific occurrence of the problem.
HTTP status code
A short, human-readable summary of the problem type. This value should not change between occurrences of the error.
A URI reference to human-readable documentation for the error.
Example
{ "$schema": "/api/v1/schemas/ErrorModel.json", "detail": "Property foo is required but is missing.", "instance": "https://example.com/error-log/abc123", "status": 400, "title": "Bad Request", "type": "about:blank"}