Resolve a batch of node ids to their display names. The shared `useEntityNames` resolver, and any table rendering a node reference by id, use this so names resolve across the **whole** fleet: the old path resolved against the first page of `list_nodes` (default 100), so a reference to the 101st node silently degraded to a raw UUID.

POST

/api/v1/node-names

curl --request POST \
  --url https://example.com/api/v1/node-names \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "ids": [ "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" ] }'

Authorizations

• bearer

Request Body^required

Media typeapplication/json

Request body for POST /api/v1/node-names: the node ids whose display names to resolve.

object

ids

required

Array<string>

Example^generated

{
  "ids": [
    "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0"
  ]
}

Responses

200

The resolved names; an id with no row is omitted

Media typeapplication/json

Array<object>

One resolved node id → display name (unresolved ids are omitted; the caller keeps the raw id).

object

id

required

string format: uuid

name

required

string

Example^generated

[
  {
    "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
    "name": "example"
  }
]

401

No valid bearer token

Media typeapplication/json

The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies undescribed — a client that has to guess the failure shape ends up parsing the success shape and reading undefined.

object

error

required

object

code

required

Stable machine-readable code. Clients branch on this, never on the message.

string

message

required

Operator-facing sentence. Safe to display; never carries an internal error’s own text.

string

Example^generated

{
  "error": {
    "code": "example",
    "message": "example"
  }
}

403

Role lacks the View permission

Media typeapplication/json

The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies undescribed — a client that has to guess the failure shape ends up parsing the success shape and reading undefined.

object

error

required

object

code

required

Stable machine-readable code. Clients branch on this, never on the message.

string

message

required

Operator-facing sentence. Safe to display; never carries an internal error’s own text.

string

Example^generated

{
  "error": {
    "code": "example",
    "message": "example"
  }
}