---
title: "Record Relationships"
method: GET
path: "/relationships/{record_id}"
---

# Record Relationships

`GET /relationships/{record_id}`

## Request

- Base URL: `https://api.colourmemory.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.colourmemory.com/relationships/{record_id}`
- Auth: none declared

What is this record connected to, and why?

Bounded on purpose: one hop, a per-predicate cap (raisable via
max_per_predicate, default 12 -- see that parameter's own comment), and the
four relationship classes returned in SEPARATE blocks so a caller cannot
mistake a computed colour distance for something a historical source said.

`include_unresolved` defaults to FALSE. Same-name candidates across sources
are the cheapest edge in the system and the easiest to misread as evidence,
so they are withheld unless asked for by name.

Truncation, at whatever cap is in effect, is never silent: `traversal.
truncated` reports how many edges of each predicate were cut, and the true
total for a predicate is always edge_count + traversal.truncated.get(that
predicate, 0) -- confirmed already correct today (2026-09-02) for real
truncated Wada records, independent of this parameter.

## Path parameters

- `record_id` string, required

## Query parameters

- `include_unresolved` boolean
- `include_computed` boolean
- `max_per_predicate` integer

## Headers

- `x-api-key` string, nullable
- `origin` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/colourmemory/apis/colour-memory-api.md) · [All operations](https://skmtc.dev/colourmemory/apis/colour-memory-api/llms.txt) · [OpenAPI document](https://skmtc.dev/colourmemory/apis/colour-memory-api/revisions/4ba028f64042?raw)