1. Docs
  2. API Reference
  3. NodeAccessResponseDto

NodeAccessResponseDto

Example

JSON
{
  "id": "string",
  "application_id": "string",
  "parent_node_id": "string",
  "node_type": "string",
  "name": "string",
  "description": "string",
  "slug": "string",
  "status": "string",
  "metadata": {},
  "created_at": "2026-04-20T12:00:00.000Z",
  "updated_at": "2026-04-20T12:00:00.000Z",
  "version": 0,
  "access_state": "accessible",
  "can_access": false,
  "can_manage": false
}

Properties

15 properties 13 required

id string Required
application_id string Required
parent_node_id string Optional
nullable
node_type string Required
name string Required
description string Optional

Optional free-text description shown under the node name.

nullable
slug string Required
status string Required
metadata object Required
created_at string Required
format: date-time
updated_at string Required
format: date-time
version number Required

Optimistic-lock version. Send back as the `If-Match` header when updating, moving, or deleting to detect concurrent edits.

access_state enum Required
Enumaccessiblecontext_only
can_access boolean Required
can_manage boolean Required
Was this page helpful?

Tell us how we can improve this guide.

Canopy