List system types
const url = 'https://example.com/api/v1/system-types';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/system-typesLists the system_type registry (the coarse taxonomy of what kind of space a system is: a boardroom, a classroom, a video wall), ordered alphabetically by label. Each row carries its parent link, so the console reconstructs the tree client-side. Distinct from standard, which is the blueprint a system conforms to. Gated by system_type:read.
Responses
Section titled “ Responses ”OK
object
A URL to the JSON Schema for this object.
object
A URL to the JSON Schema for this object.
A compact form of label; empty inherits the nearest ancestor’s
A glyph key; empty inherits the nearest ancestor’s
The system_type’s uuid, the stable handle that survives a rename
The abbrev this type would take if it stated none: the nearest ancestor’s. Absent when no ancestor states one. Served on the registry listing, on the same terms as resolved_icon
The name of the ancestor system_type inherited_abbrev comes from, which may be further up the chain than the parent
The glyph this type would take if it stated none: the nearest ancestor’s. Absent when no ancestor states one. Served on the registry listing, on the same terms as resolved_icon
The name of the ancestor system_type inherited_icon comes from, which may be further up the chain than the parent
The stem this type would take if it stated none: the nearest ancestor’s. Absent when no ancestor states one. Served on the registry listing, on the same terms as resolved_icon
The name of the ancestor system_type inherited_stem comes from, which may be further up the chain than the parent
The label template systems of this type get; empty inherits the nearest ancestor’s, then the global rule for systems
The name an operator reads and types; renameable
The parent system_type’s name, for display; absent for a root type
The parent system_type’s id, the canonical handle; absent for a root type
The glyph this type shows: its own icon, else the nearest ancestor’s. Served on the registry listing, where the whole chain is already in hand; a single-row write response does not carry it
The prefix a generated system name is built from; empty inherits the nearest ancestor’s
Example
{ "$schema": "/api/v1/schemas/ListSystemTypesOutputBody.json", "system_types": [ { "$schema": "/api/v1/schemas/SystemTypeBody.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"}