Read a component's per-interface reachability
const url = 'https://example.com/api/v1/components/example/reachability';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/components/example/reachabilityComposes, per interface, the latest reachability verdict, the probe-layer signals that compose it, and the recent verdict transitions for the availability strip. Gated by component:read; an out-of-scope component is a non-disclosing 404.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The component’s name, or a dotted address (e.g. boi.17c.415a.$comp.display-1)
The component’s name, or a dotted address (e.g. boi.17c.415a.$comp.display-1)
Responses
Section titled “ Responses ”OK
object
A URL to the JSON Schema for this object.
object
The probed endpoint (target[:port]) from the interface params
The recent verdict transitions, oldest first, for the availability strip
object
The interface’s derived name (its protocol)
The interface type (icmp, tcp, …)
The friendly string an operator reads; absent when unset, and the row then reads the derived name verbatim
The per-layer probe signals that compose the verdict
object
The property_type key of the primary signal
A human timing detail (rtt / connect time), when present
The probe layer word (ping, port)
When the signal was observed
The latest signal value (1 = reachable/open, 0 = not)
The node that probes this interface
The latest reachability verdict, or null if none yet
object
When the verdict was observed
The latest stored verdict value (up/down)
Example
{ "$schema": "/api/v1/schemas/ReachabilityOutputBody.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"}