### GET /api/v1/targets

Source: https://beta.workflowy.com/api/-reference

Lists all available targets, including user-defined shortcuts and system targets like 'inbox'. Each target object contains a unique key, its type (shortcut or system), and the name of the node it points to.

```APIDOC
## GET /api/v1/targets

### Description
Lists all available targets, including user-defined shortcuts (like "home") and system targets (like "inbox"). Each target object contains a unique key, its type (shortcut or system), and the name of the node it points to.

### Method
GET

### Endpoint
/api/v1/targets

### Parameters
No parameters required.

### Request Example
```bash
curl https://workflowy.com/api/v1/targets \
  -H "Authorization: Bearer <YOUR_API_KEY>"
```

### Response
#### Success Response (200)
- **targets** (array) - A list of target objects.
  - **key** (string) - The unique identifier for this target (e.g., "home", "inbox", "today").
  - **type** (string) - The type of target: "shortcut" or "system".
  - **name** (string | null) - The name of the node that this target points to. Returns `null` only for system targets when the target node hasn't been created yet.

#### Response Example
```json
{
  "targets": [
    {
      "key": "home",
      "type": "shortcut",
      "name": "My Home Page"
    },
    {
      "key": "inbox",
      "type": "system",
      "name": "Inbox"
    }
  ]
}
```
```

--------------------------------

### Create a Node with Markdown Formatting using WorkFlowy API

Source: https://beta.workflowy.com/api/-reference

Example of creating a node that utilizes markdown for formatting, including bold text and hyperlinks. The WorkFlowy API interprets markdown syntax to render the content appropriately.

```curl
curl -X POST https://workflowy.com/api/v1/nodes \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -d '{
    "parent_id": "inbox",
    "name": "**Important**: See [docs](https://example.com)"
  }' | jq
```

--------------------------------

### Create a Simple Node using WorkFlowy API

Source: https://beta.workflowy.com/api/-reference

Example of creating a new node with a specified parent ID, name, and position using a POST request to the WorkFlowy API. Requires an API key for authorization.

```curl
curl -X POST https://workflowy.com/api/v1/nodes \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -d '{
    "parent_id": "inbox",
    "name": "Hello API",
    "position": "top"
  }' | jq
```

--------------------------------

### List Nodes (GET /api/v1/nodes)

Source: https://beta.workflowy.com/api/-reference

Retrieves a list of child nodes for a specified parent ID. The response is unordered and requires sorting by the 'priority' field. Authentication with an API key is necessary.

```curl
curl -G https://workflowy.com/api/v1/nodes \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -d "parent_id=inbox" | jq
```

--------------------------------

### Get Node API

Source: https://beta.workflowy.com/api/-reference

Retrieves a specific node by its ID.

```APIDOC
## GET /api/nodes/:id

### Description
Retrieves the details of a specific node using its unique identifier.

### Method
GET

### Endpoint
`/api/nodes/:id`

### Parameters
#### Path Parameters
- **id** (string, required): The unique identifier of the node to retrieve.

### Response
#### Success Response (200)
- Returns the Node object (see Node Object Structure section for details).

#### Response Example
```json
{
  "id": "6ed4b9ca-256c-bf2e-bd70-d8754237b505",
  "name": "Example Node",
  "note": "This is a sample note.",
  "priority": 100,
  "data": {
    "layoutMode": "bullets"
  },
  "createdAt": 1753120779,
  "modifiedAt": 1753120850,
  "completedAt": null
}
```
```

--------------------------------

### Retrieve Node (GET /api/v1/nodes/:id)

Source: https://beta.workflowy.com/api/-reference

Fetches the details of a specific node using its unique identifier. Returns comprehensive information including ID, name, note, creation/modification timestamps, and data. Requires API key authentication.

```curl
curl -X GET https://workflowy.com/api/v1/nodes/:id \
  -H "Authorization: Bearer <YOUR_API_KEY>" | jq
```

--------------------------------

### GET /api/v1/nodes-export

Source: https://beta.workflowy.com/api/-reference

Exports all nodes from the Workflowy account. This endpoint returns a JSON object containing a list of nodes, each with its ID, name, note, parent ID, priority, completion status, data, and timestamps.

```APIDOC
## GET /api/v1/nodes-export

### Description
Exports all nodes from the Workflowy account. This endpoint returns a JSON object containing a list of nodes, each with its ID, name, note, parent ID, priority, completion status, data, and timestamps.

### Method
GET

### Endpoint
/api/v1/nodes-export

### Parameters
No parameters required.

### Request Example
```bash
curl https://workflowy.com/api/v1/nodes-export \
  -H "Authorization: Bearer <YOUR_API_KEY>"
```

### Response
#### Success Response (200)
- **nodes** (array) - A list of node objects.
  - **id** (string) - Unique identifier for the node.
  - **name** (string) - The name or text of the node.
  - **note** (string | null) - The description or note associated with the node.
  - **parent_id** (string | null) - The ID of the parent node. Null for top-level nodes.
  - **priority** (integer) - The priority level of the node.
  - **completed** (boolean) - Indicates if the node is completed.
  - **data** (object) - Additional data associated with the node, e.g., layoutMode.
  - **createdAt** (integer) - Timestamp when the node was created.
  - **modifiedAt** (integer) - Timestamp when the node was last modified.
  - **completedAt** (integer | null) - Timestamp when the node was completed.

#### Response Example
```json
{
  "nodes": [
    {
      "id": "ee1ac4c4-775e-1983-ae98-a8eeb92b1aca",
      "name": "Top Level Item",
      "note": "This is a note",
      "parent_id": null,
      "priority": 100,
      "completed": false,
      "data": {
        "layoutMode": "bullets"
      },
      "createdAt": 1753120787,
      "modifiedAt": 1753120815,
      "completedAt": null
    },
    {
      "id": "ff2bd5d5-886f-2094-bf09-b9ffa93c2bdb",
      "name": "Child Item",
      "note": null,
      "parent_id": "ee1ac4c4-775e-1983-ae98-a8eeb92b1aca",
      "priority": 200,
      "completed": false,
      "data": {
        "layoutMode": "bullets"
      },
      "createdAt": 1753120820,
      "modifiedAt": 1753120830,
      "completedAt": null
    }
  ]
}
```
```

--------------------------------

### Export All Nodes

Source: https://beta.workflowy.com/api/-reference

Returns all user's nodes as a flat list. The hierarchy must be reconstructed using `parent_id` and `priority`.

```APIDOC
## GET /api/v1/export/all

### Description
Returns all user's nodes as a flat list. Each node includes its `parent_id` field to reconstruct the hierarchy. The nodes are returned unordered - you need to build the tree structure yourself based on the `parent_id` and `priority` fields.
Note: This endpoint has a rate limit of 1 request per minute due to the potentially large response size.

### Method
GET

### Endpoint
/api/v1/export/all

### Response
#### Success Response (200)
- **nodes** (array) - An array of all node objects.
  - Each object contains:
    - **id** (string) - The unique identifier of the node.
    - **name** (string) - The name of the node.
    - **note** (string or null) - The note associated with the node.
    - **priority** (integer) - The priority of the node.
    - **data** (object) - Additional data for the node, like layout mode.
    - **createdAt** (integer) - Timestamp of node creation.
    - **modifiedAt** (integer) - Timestamp of last modification.
    - **completedAt** (integer or null) - Timestamp of completion, if applicable.
    - **parent_id** (string) - The identifier of the parent node.

#### Response Example
```json
{
  "nodes": [
    {
      "id": "ee1ac4c4-775e-1983-ae98-a8eeb92b1aca",
      "name": "Bullet A",
      "note": null,
      "priority": 100,
      "data": {
        "layoutMode": "bullets"
      },
      "createdAt": 1753120787,
      "modifiedAt": 1753120815,
      "completedAt": null,
      "parent_id": "inbox"
    }
  ]
}
```
```

--------------------------------

### List Targets using curl

Source: https://beta.workflowy.com/api/-reference

This code snippet shows how to retrieve a list of all available targets in Workflowy, including system targets like 'inbox' and user-defined shortcuts. It uses a cURL command with an authorization header and pipes the output to `jq` for formatting. The response is a JSON object containing an array of target objects, each with a key, type, and name.

```shell
curl https://workflowy.com/api/v1/targets \
  -H "Authorization: Bearer <YOUR_API_KEY>" | jq
      
```

--------------------------------

### Create Node (POST /api/v1/nodes)

Source: https://beta.workflowy.com/api/-reference

Creates a new node with a specified name and parent. Requires authentication with an API key. The response includes the status of the operation.

```curl
curl -X POST https://workflowy.com/api/v1/nodes \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -d '{
    "parent_id": "inbox",
    "name": "Meeting [2025-12-15 14:30]"
  }' | jq
```

--------------------------------

### Target Object Structure

Source: https://beta.workflowy.com/api/-reference

This section illustrates the structure of a Target object in Workflowy. Targets represent shortcuts to specific nodes. The object includes a unique `key`, a `type` (either 'shortcut' or 'system'), and the `name` of the node it points to, which can be null for system targets if the node hasn't been created.

```json
{
  "key": "home",
  "type": "shortcut",
  "name": "My Home Page"
}
      
```

```json
{
  "key": "inbox",
  "type": "system",
  "name": null
}
      
```

--------------------------------

### Export All Nodes

Source: https://beta.workflowy.com/api/-reference

Retrieves all nodes belonging to the user as a flat list. Each node contains a `parent_id` for reconstructing the hierarchy. Nodes are unordered and require sorting by `priority`. This endpoint has a rate limit of 1 request per minute.

--------------------------------

### Complete Node

Source: https://beta.workflowy.com/api/-reference

Marks a node as completed, setting its completion timestamp.

```APIDOC
## POST /api/v1/nodes/:id/complete

### Description
Marks a node as completed. This sets the completion timestamp and updates the node's status.

### Method
POST

### Endpoint
/api/v1/nodes/:id/complete

### Parameters
#### Path Parameters
- **id** (string) - Required - The identifier of the node to complete.

### Response
#### Success Response (200)
- **status** (string) - Indicates the success of the operation, typically "ok".

#### Response Example
```json
{
  "status": "ok"
}
```
```

--------------------------------

### Complete Node (POST /api/v1/nodes/:id/complete)

Source: https://beta.workflowy.com/api/-reference

Marks a specified node as completed by setting its completion timestamp. Requires the node's ID and API key authentication. The response indicates the success status.

```curl
curl -X POST https://workflowy.com/api/v1/nodes/:id/complete \
  -H "Authorization: Bearer <YOUR_API_KEY>" | jq
```

--------------------------------

### Export Nodes using curl

Source: https://beta.workflowy.com/api/-reference

This snippet demonstrates how to export all nodes from your Workflowy outline using a cURL command. It requires an API key for authorization and pipes the output to `jq` for pretty-printing. The response is a JSON object containing an array of nodes, each with detailed properties like ID, name, notes, and timestamps.

```shell
curl https://workflowy.com/api/v1/nodes-export \
  -H "Authorization: Bearer <YOUR_API_KEY>" | jq
      
```

--------------------------------

### List Nodes

Source: https://beta.workflowy.com/api/-reference

Returns a list of child nodes for a given parent. Nodes are returned unordered and should be sorted by the `priority` field.

```APIDOC
## GET /api/v1/nodes

### Description
Returns a list of child nodes for a given parent. The nodes are returned unordered - you need to sort them yourself based on the `priority` field.

### Method
GET

### Endpoint
/api/v1/nodes

### Parameters
#### Query Parameters
- **parent_id** (string) - Optional - The parent node identifier. Can be a node UUID, a target key (e.g., "home", "inbox"), or "None" to list top-level nodes.

### Response
#### Success Response (200)
- **nodes** (array) - An array of node objects.
  - Each object contains:
    - **id** (string) - The unique identifier of the node.
    - **name** (string) - The name of the node.
    - **note** (string or null) - The note associated with the node.
    - **priority** (integer) - The priority of the node.
    - **data** (object) - Additional data for the node, like layout mode.
    - **createdAt** (integer) - Timestamp of node creation.
    - **modifiedAt** (integer) - Timestamp of last modification.
    - **completedAt** (integer or null) - Timestamp of completion, if applicable.

#### Response Example
```json
{
  "nodes": [
    {
      "id": "ee1ac4c4-775e-1983-ae98-a8eeb92b1aca",
      "name": "Bullet A",
      "note": null,
      "priority": 100,
      "data": {
        "layoutMode": "bullets"
      },
      "createdAt": 1753120787,
      "modifiedAt": 1753120815,
      "completedAt": null
    }
  ]
}
```
```

--------------------------------

### Move Node (POST /api/v1/nodes/:id/move)

Source: https://beta.workflowy.com/api/-reference

Moves a node to a new parent and optionally to a specific position ('top' or 'bottom'). Requires the node's ID and the new parent's ID. Authentication with an API key is mandatory.

```curl
curl -X POST https://workflowy.com/api/v1/nodes/<NODE_ID>/move \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -d '{
    "parent_id": "inbox",
    "position": "top"
  }' | jq
```

--------------------------------

### Create Node API

Source: https://beta.workflowy.com/api/-reference

Allows for the creation of new nodes within the WorkFlowy structure.

```APIDOC
## POST /api/v1/nodes

### Description
Creates a new node in WorkFlowy. You can specify the parent node, name, note, layout mode, and position for the new node.

### Method
POST

### Endpoint
`/api/v1/nodes`

### Parameters
#### Request Body
- **parent_id** (string): The parent node identifier. Can be a node UUID, a target key (e.g., `"home"`, `"inbox"`), or `"None"` to create a top-level node.
- **name** (string, required): The text content of the new node. Supports formatting.
- **note** (string): Additional note content for the node.
- **layoutMode** (string): The display mode of the node. Common values include `"bullets"` (default), `"todo"`, `"h1"`, `"h2"`, `"h3"`.
- **position** (string): Where to place the new node. Options: `"top"` (default) or `"bottom"`.

### Request Example (Basic)
```json
{
  "parent_id": "inbox",
  "name": "Hello API",
  "position": "top"
}
```

### Request Example (With Formatting)
```json
{
  "parent_id": "inbox",
  "name": "# Project\n\n- [ ] Task one\n\n- [ ] Task two"
}
```

### Request Example (With Markdown Link)
```json
{
  "parent_id": "inbox",
  "name": "**Important**: See [docs](https://example.com)"
}
```

### Response
#### Success Response (200)
- **item_id** (string): The unique identifier of the newly created node.

#### Response Example
```json
{
  "item_id": "5b401959-4740-4e1a-905a-62a961daa8c9"
}
```
```

--------------------------------

### Create a Node with Nested Structure using WorkFlowy API

Source: https://beta.workflowy.com/api/-reference

Demonstrates creating a node that includes a nested structure of child nodes using markdown syntax within the 'name' field. The API parses markdown to create a parent with bulleted and todo list children.

```curl
curl -X POST https://workflowy.com/api/v1/nodes \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -d '{
    "parent_id": "inbox",
    "name": "# Project\n\n- [ ] Task one\n\n- [ ] Task two"
  }' | jq
```

--------------------------------

### Uncomplete Node (POST /api/v1/nodes/:id/uncomplete)

Source: https://beta.workflowy.com/api/-reference

Marks a specified node as not completed by removing its completion timestamp. Requires the node's ID and API key authentication. The operation's status is returned in the response.

```curl
curl -X POST https://workflowy.com/api/v1/nodes/:id/uncomplete \
  -H "Authorization: Bearer <YOUR_API_KEY>" | jq
```

--------------------------------

### Create Node

Source: https://beta.workflowy.com/api/-reference

Creates a new node within the WorkFlowy system. You can specify the parent node and the name of the new node.

```APIDOC
## POST /api/v1/nodes

### Description
Creates a new node.

### Method
POST

### Endpoint
/api/v1/nodes

### Parameters
#### Request Body
- **parent_id** (string) - Required - The ID of the parent node where the new node will be created.
- **name** (string) - Required - The name of the new node.

### Request Example
```json
{
  "parent_id": "inbox",
  "name": "Meeting [2025-12-15 14:30]"
}
```

### Response
#### Success Response (200)
- **node** (object) - The created node object.
  - **id** (string) - The unique identifier of the created node.
  - **name** (string) - The name of the created node.
  - **note** (string or null) - The note associated with the node.
  - **priority** (integer) - The priority of the node.
  - **data** (object) - Additional data for the node, like layout mode.
  - **createdAt** (integer) - Timestamp of node creation.
  - **modifiedAt** (integer) - Timestamp of last modification.
  - **completedAt** (integer or null) - Timestamp of completion, if applicable.

#### Response Example
```json
{
  "node": {
    "id": "6ed4b9ca-256c-bf2e-bd70-d8754237b505",
    "name": "Meeting [2025-12-15 14:30]",
    "note": null,
    "priority": 100,
    "data": {
      "layoutMode": "bullets"
    },
    "createdAt": 1753120779,
    "modifiedAt": 1753120850,
    "completedAt": null
  }
}
```
```

--------------------------------

### Retrieve Node

Source: https://beta.workflowy.com/api/-reference

Retrieves the details of a specific node using its unique ID.

```APIDOC
## GET /api/v1/nodes/:id

### Description
Retrieves the details of an existing node. Supply the unique node ID and WorkFlowy will return the corresponding node information.

### Method
GET

### Endpoint
/api/v1/nodes/:id

### Parameters
#### Path Parameters
- **id** (string) - Required - The identifier of the node to retrieve.

### Response
#### Success Response (200)
- **node** (object) - The requested node object.
  - **id** (string) - The unique identifier of the node.
  - **name** (string) - The name of the node.
  - **note** (string or null) - The note associated with the node.
  - **priority** (integer) - The priority of the node.
  - **data** (object) - Additional data for the node, like layout mode.
  - **createdAt** (integer) - Timestamp of node creation.
  - **modifiedAt** (integer) - Timestamp of last modification.
  - **completedAt** (integer or null) - Timestamp of completion, if applicable.

#### Response Example
```json
{
  "node": {
    "id": "6ed4b9ca-256c-bf2e-bd70-d8754237b505",
    "name": "This is a test outline for API examples",
    "note": null,
    "priority": 200,
    "data": {
      "layoutMode": "bullets"
    },
    "createdAt": 1753120779,
    "modifiedAt": 1753120850,
    "completedAt": null
  }
}
```
```

--------------------------------

### Uncomplete Node

Source: https://beta.workflowy.com/api/-reference

Marks a node as not completed, removing its completion timestamp.

```APIDOC
## POST /api/v1/nodes/:id/uncomplete

### Description
Marks a node as not completed. This removes the completion timestamp and updates the node's status.

### Method
POST

### Endpoint
/api/v1/nodes/:id/uncomplete

### Parameters
#### Path Parameters
- **id** (string) - Required - The identifier of the node to uncomplete.

### Response
#### Success Response (200)
- **status** (string) - Indicates the success of the operation, typically "ok".

#### Response Example
```json
{
  "status": "ok"
}
```
```

--------------------------------

### Update Node

Source: https://beta.workflowy.com/api/-reference

Updates an existing node. You can modify its name, note, or layout mode. Fields not provided will remain unchanged.

```APIDOC
## POST /api/v1/nodes/:id

### Description
Updates the specified node by setting the values of the parameters passed. Any parameters not provided will be left unchanged.

### Method
POST

### Endpoint
/api/v1/nodes/:id

### Parameters
#### Path Parameters
- **id** (string) - Required - The identifier of the node to update.

#### Request Body
- **name** (string) - Optional - The text content of the node. Supports formatting.
- **note** (string) - Optional - The note content of the node.
- **layoutMode** (string) - Optional - The display mode of the node.

### Request Example
```json
{
  "name": "Updated node title"
}
```

### Response
#### Success Response (200)
- **status** (string) - Indicates the success of the operation, typically "ok".

#### Response Example
```json
{
  "status": "ok"
}
```
```

--------------------------------

### Update Node API

Source: https://beta.workflowy.com/api/-reference

Updates an existing node's properties.

```APIDOC
## POST /api/nodes/:id

### Description
Updates the properties of an existing node. You can modify its name, note, priority, or layout mode.

### Method
POST

### Endpoint
`/api/nodes/:id`

### Parameters
#### Path Parameters
- **id** (string, required): The unique identifier of the node to update.

#### Request Body
- **name** (string, optional): The new text content for the node.
- **note** (string, optional): The new additional note content for the node.
- **priority** (number, optional): The new sort order for the node among its siblings.
- **data.layoutMode** (string, optional): The new display mode for the node (e.g., `"bullets"`, `"todo"`).

### Request Example
```json
{
  "name": "Updated Node Name",
  "note": "This note has been updated."
}
```

### Response
#### Success Response (200)
- Typically returns the updated Node object or a success status.

#### Response Example
```json
{
  "message": "Node updated successfully.",
  "updatedNodeId": "6ed4b9ca-256c-bf2e-bd70-d8754237b505"
}
```
```

--------------------------------

### Move Node

Source: https://beta.workflowy.com/api/-reference

Moves a node to a new parent and/or position within the hierarchy.

```APIDOC
## POST /api/v1/nodes/:id/move

### Description
Moves a node to a different parent and/or position.

### Method
POST

### Endpoint
/api/v1/nodes/:id/move

### Parameters
#### Path Parameters
- **id** (string) - Required - The identifier of the node to move.

#### Request Body
- **parent_id** (string) - Optional - The new parent node identifier. Can be a node UUID, a target key (e.g., "home", "inbox"), or "None" to move to top-level.
- **position** (string) - Optional - Where to place the node. Options: "top" (default) or "bottom".

### Request Example
```json
{
  "parent_id": "inbox",
  "position": "top"
}
```

### Response
#### Success Response (200)
- **status** (string) - Indicates the success of the operation, typically "ok".

#### Response Example
```json
{
  "status": "ok"
}
```
```

--------------------------------

### List Nodes API

Source: https://beta.workflowy.com/api/-reference

Retrieves a list of nodes. This endpoint can be used to fetch all top-level nodes or nodes within a specific parent.

```APIDOC
## GET /api/nodes

### Description
Retrieves a list of nodes. By default, it returns top-level nodes. You can specify a `parentId` to get children of a specific node.

### Method
GET

### Endpoint
`/api/nodes`

### Parameters
#### Query Parameters
- **parentId** (string, optional): The ID of the parent node whose children should be retrieved. If omitted, top-level nodes are returned.

### Response
#### Success Response (200)
- Returns an array of Node objects.

#### Response Example (Top-level nodes)
```json
[
  {
    "id": "node-id-1",
    "name": "First Top Level Node",
    "priority": 100,
    "createdAt": 1753120779,
    "modifiedAt": 1753120850
  },
  {
    "id": "node-id-2",
    "name": "Second Top Level Node",
    "priority": 200,
    "createdAt": 1753120900,
    "modifiedAt": 1753120950
  }
]
```

#### Response Example (Children of a specific node)
```json
[
  {
    "id": "child-node-id-1",
    "name": "Child Node 1",
    "priority": 100,
    "createdAt": 1753121000,
    "modifiedAt": 1753121050
  }
]
```
```

--------------------------------

### Update Node (POST /api/v1/nodes/:id)

Source: https://beta.workflowy.com/api/-reference

Updates an existing node identified by its ID. Allows modification of the node's name, note, or layout mode. Parameters not provided will remain unchanged. Authentication is required.

```curl
curl -X POST https://workflowy.com/api/v1/nodes/:id \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -d '{
    "name": "Updated node title"
  }' | jq
```

--------------------------------

### Node Object Structure

Source: https://beta.workflowy.com/api/-reference

Describes the structure and attributes of a node object in WorkFlowy.

```APIDOC
## Node Object Structure

### Description
A node is the fundamental unit of content in WorkFlowy. Each node represents a single bullet point that can contain text, have child nodes, and be organized hierarchically. Nodes can be expanded or collapsed, completed, tagged, and moved around to create flexible outlines and lists.

### Attributes
- **id** (string): Unique identifier of the node.
- **name** (string): The text content of the node. Supports formatting.
- **note** (string | null): Additional note content for the node. Notes appear below the main text.
- **priority** (number): Sort order of the node among its siblings. Lower values appear first.
- **data.layoutMode** (string): Display mode of the node. Common values include `"bullets"` (default), `"todo"`, `"h1"`, `"h2"`, `"h3"`.
- **createdAt** (number): Unix timestamp indicating when the node was created.
- **modifiedAt** (number): Unix timestamp indicating when the node was last modified.
- **completedAt** (number | null): Unix timestamp indicating when the node was completed. `null` if the node is not completed.

### Example Node Object
```json
{
  "id": "6ed4b9ca-256c-bf2e-bd70-d8754237b505",
  "name": "This is a test outline for API examples",
  "note": null,
  "priority": 200,
  "data": {
    "layoutMode": "bullets"
  },
  "createdAt": 1753120779,
  "modifiedAt": 1753120850,
  "completedAt": null
}
```
```

--------------------------------

### Delete Node (DELETE /api/v1/nodes/:id)

Source: https://beta.workflowy.com/api/-reference

Permanently deletes a node identified by its ID. This action is irreversible. API key authentication is required to perform this operation.

```curl
curl -X DELETE https://workflowy.com/api/v1/nodes/:id \
  -H "Authorization: Bearer <YOUR_API_KEY>" | jq
```

--------------------------------

### Delete Node

Source: https://beta.workflowy.com/api/-reference

Permanently deletes a specified node. This action is irreversible.

```APIDOC
## DELETE /api/v1/nodes/:id

### Description
Permanently deletes a node. This cannot be undone.

### Method
DELETE

### Endpoint
/api/v1/nodes/:id

### Parameters
#### Path Parameters
- **id** (string) - Required - The identifier of the node to delete.

### Response
#### Success Response (200)
- **status** (string) - Indicates the success of the operation, typically "ok".

#### Response Example
```json
{
  "status": "ok"
}
```
```

--------------------------------

### Delete Node API

Source: https://beta.workflowy.com/api/-reference

Deletes a specific node by its ID.

```APIDOC
## DELETE /api/nodes/:id

### Description
Deletes a specific node and all its descendants.

### Method
DELETE

### Endpoint
`/api/nodes/:id`

### Parameters
#### Path Parameters
- **id** (string, required): The unique identifier of the node to delete.

### Response
#### Success Response (200)
- Typically returns a confirmation message or status.

#### Response Example
```json
{
  "message": "Node and its descendants deleted successfully."
}
```
```

--------------------------------

### WorkFlowy Node Object Structure

Source: https://beta.workflowy.com/api/-reference

The Node object represents a single bullet point in WorkFlowy and contains attributes such as ID, name, note, priority, layout mode, and timestamps for creation, modification, and completion.

```json
{
  "id": "6ed4b9ca-256c-bf2e-bd70-d8754237b505",
  "name": "This is a test outline for API examples",
  "note": null,
  "priority": 200,
  "data": {
    "layoutMode": "bullets"
  },
  "createdAt": 1753120779,
  "modifiedAt": 1753120850,
  "completedAt": null
}
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.