get_element_history

Who changed a node or relationship, when, and with which operation. It reads from the model's change journal, so it also works for deleted elements. Each entry gives the operation, the time and who made it: a person in the app, the AI assistant, or an API token or OAuth user over MCP. An update entry also lists the fields it set. A delete entry also says whether the element can be restored now, and its op_id is what restore_deleted_elements takes. Each response includes journal_starts_at: an empty history means nothing changed since then, not that the element never changed. element_id accepts a UUID or an auto-ID. Auto-IDs are reused after a delete, so an ambiguous one returns candidates. The newest entries come back first; to page further back, pass next_before_seq as before_seq.

{"element_id": "HA-30", "limit": 20}

{"element_id": "73658a7b-591b-498b-961b-29be5ae499fe", "entries": [{"op_id": 78720, "seq": 1373, "op_type": "NodeUpdated", "actor_id": "mcp", "actor_kind": "mcp", "fields": ["description", "property_values"], "server_ts": "2026-09-04T06:12:06.802Z"}], "journal_starts_at": "2026-07-02T09:57:20.593Z", "next_before_seq": 1373}