Skip to content

Put a component in a system

PUT
/systems/{name}/members/{component}
curl --request PUT \
--url https://example.com/api/v1/systems/example/members/example

Binds this component into the system. Idempotent. A component’s first membership becomes its primary with nobody asking, so a component in exactly one system never has to think about the concept; a later membership does not take that default away. Gated by system:update; read and update scopes drive the 404 versus 403 split.

name
required

Name of the system, or a dotted address (e.g. boi.17c.$sys.av)

string

Name of the system, or a dotted address (e.g. boi.17c.$sys.av)

component
required

Name of the component, or a dotted address (e.g. boi.17c.415a.$comp.display-1)

string

Name of the component, or a dotted address (e.g. boi.17c.415a.$comp.display-1)

No Content

Error

Media type application/problem+json
object
$schema

A URL to the JSON Schema for this object.

string format: uri
detail

A human-readable explanation specific to this occurrence of the problem.

string
errors

Optional list of individual error details

Array<object> | null
object
location

Where the error occurred, e.g. ‘body.items[3].tags’ or ‘path.thing-id’

string
message

Error message text

string
value

The value at the given location

instance

A URI reference that identifies the specific occurrence of the problem.

string format: uri
status

HTTP status code

integer format: int64
title

A short, human-readable summary of the problem type. This value should not change between occurrences of the error.

string
type

A URI reference to human-readable documentation for the error.

string format: uri
default: about:blank
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"
}