Skip to main content
GET
Get a graph node
Scoped to the effective subject (the API key owner by default, or the subject named by X-Exo-Subject). A node belonging to another subject or another org returns 404.

Authorization

This route requires the read scope. A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.

Headers

These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.

Success responses

Errors

Every error is an RFC 9457 application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Path Parameters

node_id
string
required

Response

The node, its content and its strongest neighbouring edges.

Full node detail for GET /api/v1/graph/nodes/{nodeId} (Story 4-4).

Single-item response (unwrapped, ARCH-19). Includes content, metadata, connected edges with neighbor labels, domain, and projects. Reusable across dashboard click, project view, and context trace.

id
string
required
label
string
required
nodeType
string
required
authorityLevel
number
default:1
content
string | null
createdAt
string
default:""
decayRate
number
default:0
domain
string | null
domains
Domains · object | null
edges
GraphNodeDetailEdge · object[]
origin
string | null
projects
string[]