Reorder board nodes

Set the order of a board's nodes. You send the whole order, not one node's new place, and the board is rewritten in a single write.

Needs edit access to the board, described under Who can edit a board.

Request#

Read the board, move the IDs, send them back:

curl -X PUT https://api2.rundiffusion.com/api/v2/boards/$BOARD_ID/nodes/position \
  -H "Authorization: Bearer $RUNDIFFUSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"node_ids": ["Nd7mQp…", "Nd4kWs…"]}'

// Move the last node to the front.
const board = await fetch(
  `https://api2.rundiffusion.com/api/v2/boards/${boardId}`,
  { headers },
).then(r => r.json());

const ids = board.nodes.map(node => node.id);
ids.unshift(ids.pop());

const nodes = await fetch(
  `https://api2.rundiffusion.com/api/v2/boards/${boardId}/nodes/position`,
  {
    method: 'PUT',
    headers: { ...headers, 'Content-Type': 'application/json' },
    body: JSON.stringify({ node_ids: ids }),
  },
).then(r => r.json());

# Move the last node to the front.
board = requests.get(
    f"{BASE}/boards/{board_id}",
    headers=HEADERS,
).json()

ids = [node["id"] for node in board["nodes"]]
ids.insert(0, ids.pop())

nodes = requests.put(
    f"{BASE}/boards/{board_id}/nodes/position",
    headers=HEADERS,
    json={"node_ids": ids},
).json()

Response#

200 OK with every node in its new order, each carrying its new position.list_view_index. The array is the board, so you can render from it without refetching.

[
  {
    "id": "Nd7mQp…",
    "created_at": "2026-07-30T14:05:44+00:00",
    "title": "Upscale",
    "description": null,
    "tool_id": "Tl2cRn…",
    "position": { "list_view_index": 0 }
  },
  {
    "id": "Nd4kWs…",
    "created_at": "2026-07-30T14:03:02+00:00",
    "title": "Flux Dev",
    "description": "Text to image",
    "tool_id": "Tl9xBv…",
    "position": { "list_view_index": 1 }
  }
]

Why the whole list#

Sending one node's new index would look simpler and would be unsafe. An index only means something against a particular set of nodes, so if somebody adds or removes a node between your read and your write, "move this to index 3" lands somewhere you did not intend, and nothing detects it.

The full list makes that impossible to miss. It has to match the board exactly, so if the board changed under you the request is refused rather than applied to a board you have not seen:

Every node is rewritten on each call, so the order is always dense and 0-based afterwards, whatever state it was in before.

Errors#