The nodes one relation joins a node to, a page at a time
const url = 'https://example.com/v1/orgs/example/graph/nodes/example/neighbours?relation=example&direction=out';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
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/v1/orgs/example/graph/nodes/example/neighbours?relation=example&direction=out' \ --header 'Authorization: Bearer <token>'Follows one relation in one direction, 100 neighbours per page; the first node is the one asked about. Edges always point the relation’s way. From a public node (a vulnerability, KEV entry or EPSS score) back to tenant data, only this organization’s nodes are reached.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Organization (tenant) slug, e.g. alpenrobotik
A node ID: urn:affectra:
Query Parameters
Section titled “Query Parameters”A relation from the ontology (GraphEdge.relation), e.g. dependsOn, matches, hasFinding
Out (from the relation’s from-class, the default) or in
The next of the previous page
Responses
Section titled “Responses”The node and its neighbours; truncated and next when there are more
The envelope of every graph answer.
object
Traversal-specific (
object
object
Urn:affectra:… for tenant and shared nodes; public nodes keep their own IDs (CVE-…, CWE-79).
Composed from first-party data only; empty when the ID is the label.
Only the properties the ontology lists for the class (
object
A relation between two nodes. Agents cite edges as evidence.
object
Node ID.
Node ID.
The relation’s properties, e.g. MatchesEdgeProperties.
object
A limit cut the result.
Opaque cursor for the next page.
When the data was read.
The version of each feed the answer used (feed_state), e.g. osv, nvd, kev, epss.
object
How current each feed is, by feed_state key (osv:Debian, kev, epss, nvd), including feeds with no version yet. Say how old the data is from checked_at; state says whether that is old enough to matter. Times and states only.
object
object
The last attempt that succeeded, changed or not; null if the feed has never been checked.
False when the organization turned this feed off: findings that only it reports are hidden, not deleted (list_feeds names the feeds and who changed them). True for every other feed.
From the age of checked_at against the feed’s thresholds (libs/go/feedhealth); never checked is very_stale.
Example
{ "nodes": [ { "class": "Artifact" } ], "edges": [ { "relation": "about" } ], "feed_status": { "additionalProperty": { "state": "ok" } }}Missing or unknown relation, a relation that doesn’t touch the node’s class, a bad direction or cursor
No such object in this organization, no such organization, or the caller does not belong to it
Over the operation’s rate-limit budget (x-affectra-budget): code request.rateLimited with params.budget. Wait Retry-After seconds before trying again.
Every error answer, Content-Type
application/problem+json. The web app and integrations translate code; detail is English,
for people reading curl output or CI logs, and may change wording at
any time. Match on code, never on detail.
object
The HTTP status
Stable error codes. A code is never renamed; new ones may be added, so
a client falls back to detail for a code it doesn’t know. Another
organization’s object answers notFound, the same as a missing one.
What went wrong
Values the code’s message needs, e.g. {“field”: “version”}. Only values the caller sent or may see. Empty when the message needs none.
object
Example
{ "code": "notFound"}Headers
Section titled “Headers”Seconds until a request would be allowed again, at least 1
The server runs without a database (catalog.unavailable), or the query ran past its statement timeout (graph.timeout); try again