---
title: "Record Combination Companions"
method: GET
path: "/relationships/{record_id}/combinations"
---

# Record Combination Companions

`GET /relationships/{record_id}/combinations`

## 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}/combinations`
- Auth: none declared

Every colour published alongside this one, across every combination.

One call, one metered charge, however many combinations the record has.

A companion's hex is null when the name did not resolve to an
INDEPENDENTLY CONFIRMED record from the same archive -- never a guessed
hex. The name still comes back; only the swatch is withheld. This is the
same drop-rather-than-guess discipline _load_name_index() already applies
server-side, and the same one the plugin applied client-side before this
endpoint existed (isVerifiedWadaLookup) -- moved, not relaxed.

Rides an open plugin trial rather than charging one of its own: the Wada
section is part of the selection the passport has already charged for.

## Path parameters

- `record_id` string, required

## 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)